Skip to content

Commit 1f92e03

Browse files
authored
Minor vale error fixes (#564)
1 parent 069b536 commit 1f92e03

2 files changed

Lines changed: 5 additions & 5 deletions

File tree

modules/ROOT/pages/manage-client-apps-connected-apps-concept.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ The connected app can manage the client application it created, and can perform
3535
* Request a tier change
3636
* Reset a client applications secret
3737

38-
You cannot add a connected app as an owner of a client application. Connected apps can only manage the client applications they create.
38+
You can't add a connected app as an owner of a client application. Connected apps can only manage the client applications they create.
3939

4040
== Creating a Client Application with the API Manager API
4141

@@ -66,7 +66,7 @@ curl --location --request POST 'https://anypoint.mulesoft.com/accounts/api/v2/oa
6666
. Collect the following information to create your client application:
6767

6868
* `<your-org-id>`: *Organization ID* for the organization where you want to create the connected app
69-
* `<instance-id>`: API instance ID of the API instance you are creating a client application for
69+
* `<instance-id>`: API instance ID of the API instance you're creating a client application for
7070
* Client Application parameters:
7171
** `name`: Name of the application
7272
** `description`: Description of the application

modules/ROOT/pages/rest-validator-extension.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ endif::[]
55

66
The REST validator extension enables you to perform schema validations that use a RAML or OAS specification against the attributes of a request. Additionally, the extension adds default values to attributes, if they are already not set in the request.
77

8-
Unless otherwise noted, this documentation applies exclusively to REST validator extension v2.x. To use the REST validator extension in your Mule artifact, such as a Mule runtime engine (Mule) application XML, you must:
8+
Unless otherwise noted, this documentation applies only to REST validator extension v2.x. To use the REST validator extension in your Mule artifact, such as a Mule runtime engine (Mule) application XML, you must:
99

1010
. <<include-dependency,Include the dependency in your pom.xml file>>.
1111
. <<add-namespace-and-schema,Add the namespace and schema to your Mule artifact>>.
@@ -97,7 +97,7 @@ If the request does not violate the defined schema, the validation ends successf
9797

9898
*Error Types*
9999

100-
The validate-request operation might raise different errors if a problem occurs when retrieving a file or if the validation does not end successfully:
100+
The `validate-request` operation might raise different errors if a problem occurs when retrieving a file or if the validation does not end successfully:
101101

102102
* `REST-VALIDATOR:BAD_REQUEST`
103103
+
@@ -143,7 +143,7 @@ If you must use the console operation, set this property to `true`. The default
143143
If you are using a REST validator version that is later than 2.0.0, use the `keepRamlBaseUri` attribute. | No
144144
| `queryParamsStrictValidation` | Validates whether all the query parameters in the request are defined in the specification file. If some of the parameters are not specified, the validation fails. The default value is `false`. | No
145145
| `headersStrictValidation` | Validates whether all the required headers defined in the specification are defined in the request. If some of the parameters are not specified, the validation fails. The default value is `false`. | No
146-
| attributesDeserializingStrategies` | Allows parsing of the HTTP headers that contain an array of values that are separated by commas. | No
146+
| `attributesDeserializingStrategies` | Allows parsing of the HTTP headers that contain an array of values that are separated by commas. | No
147147
|===
148148

149149
== REST Validator and APIkit Compatibility Reference

0 commit comments

Comments
 (0)