From 39da242f382591a9f7d2c4307a48b5e6c805f9be Mon Sep 17 00:00:00 2001 From: Todd Knight Date: Tue, 29 Sep 2020 15:11:26 -0700 Subject: [PATCH] Removing a few incorrect statements in the documentation. (#498) --- website/content/docs/common-workflows/manage-scopes.mdx | 2 +- website/content/docs/concepts/api-standards.mdx | 4 +--- 2 files changed, 2 insertions(+), 4 deletions(-) diff --git a/website/content/docs/common-workflows/manage-scopes.mdx b/website/content/docs/common-workflows/manage-scopes.mdx index dd4e8c3a35..09009fb6e9 100644 --- a/website/content/docs/common-workflows/manage-scopes.mdx +++ b/website/content/docs/common-workflows/manage-scopes.mdx @@ -13,7 +13,7 @@ Scopes are a foundational part of Boundary. They allow users to segregate resour 2. Organization 3. Project -Some resources can only be associated with a specific level of scope. Targets for example can only be project scope. Other resources can be of two scopes. For example, users can be both organization and project level scope. See the [domain model](/docs/domain-model) for detailed resource specific information. +Some resources can only be associated with a specific level of scope. Targets for example can only be project scope. Other resources can be of multiple scopes. For example, users can be both global and organization level scoped. See the [domain model](/docs/domain-model) for detailed resource specific information. In this example, we're going to create two scopes, a project and an organization. diff --git a/website/content/docs/concepts/api-standards.mdx b/website/content/docs/concepts/api-standards.mdx index ed6d7026ba..ab5921acff 100644 --- a/website/content/docs/concepts/api-standards.mdx +++ b/website/content/docs/concepts/api-standards.mdx @@ -75,8 +75,6 @@ The following method conventions are used within Boundary's API: * Passing a JSON `null` for a parameter has the effect of reverting that parameter to its default. For some parameters (e.g. `name`) this will simply clear the value (as the default `name` for a resource is empty); for other parameters this will revert to the current defaults within Boundary. * All parameters specified as part of a `PATCH` operation will be considered to be parameters that should be updated. -For clients that have difficulty choosing which parameters to include in a request, for most paths an alternative form is allowed where the parameters of the resource can be specified in a JSON object under the key `item` and an `update_mask` parameter containing a comma-separate list of field names that should actually be used for the update operation is included. - ### DELETE -`DELETE` is used for deleting a specific resource, and is only used against a particular resource path. \ No newline at end of file +`DELETE` is used for deleting a specific resource, and is only used against a particular resource path.