style

Author: dlepow

articles/api-management/authentication-managed-identity-policy.md

@@ -29,7 +29,7 @@ Both system-assigned identity and any of the multiple user-assigned identities c
 | Attribute         | Description                                            | Required | Default |
 | ----------------- | ------------------------------------------------------ | -------- | ------- |
 |resource|String. The application ID of the target web API (secured resource) in Azure Active Directory. Policy expressions are allowed. |Yes|N/A|
-|client-id|String. The client ID of the user-assigned identity in Azure Active Directory. Policy expressions are not allowed. |No|system-assigned identity|
+|client-id|String. The client ID of the user-assigned identity in Azure Active Directory. Policy expressions aren't allowed. |No|system-assigned identity|
 |output-token-variable-name|String. Name of the context variable that will receive token value as an object of type `string`. Policy expresssions are not allowed. |No|N/A|  
 |ignore-error|Boolean. If set to `true`, the policy pipeline will continue to execute even if an access token is not obtained.|No|`false`|  
 

articles/api-management/emit-metric-policy.md

@@ -32,8 +32,8 @@ The `emit-metric` policy sends custom metrics in the specified format to Applica
 
 | Attribute | Description                | Required                | Default value  |
 | --------- | -------------------------- |  ------------------ | -------------- |
-| name      | Name of custom metric. Policy expressions are not allowed.      | Yes       | N/A            |
-| namespace | Namespace of custom metric. Policy expressions are not allowed. | No        | API Management |
+| name      | A string. Name of custom metric. Policy expressions aren't allowed.      | Yes       | N/A            |
+| namespace | A string. Namespace of custom metric. Policy expressions aren't allowed. | No        | API Management |
 | value     |  Value of custom metric expressed as an integer. Policy expressions are allowed.   | No           | 1              |
 
 

articles/api-management/forward-request-policy.md

@@ -33,8 +33,8 @@ The `forward-request` policy forwards the incoming request to the backend servic
 | timeout                             | The amount of time in seconds to wait for the HTTP response headers to be returned by the backend service before a timeout error is raised. Minimum value is 0 seconds. Values greater than 240 seconds may not be honored, because the underlying network infrastructure can drop idle connections after this time. Policy expressions are allowed. | No       | 300    |
 | follow-redirects | Specifies whether redirects from the backend service are followed by the gateway or returned to the caller. Policy expressions are allowed.                                                                                                                                                                                                    | No       | `false`   |
 | buffer-request-body      | When set to `true`, request is buffered and will be reused on [retry](retry-policy.md).                                                                                                                                                                                               | No       | `false`   |
-| buffer-response | Affects processing of chunked responses. When set to `false`, each chunk received from the backend is immediately returned to the caller. When set to `true`, chunks are buffered (8 KB, unless end of stream is detected) and only then returned to the caller.<br/><br/>Set to `false` with backends such as those implementing [server-sent events (SSE)](how-to-server-sent-events.md) that require content to be returned or streamed immediately to the caller. Policy expressions are not allowed. | No | `true` |
-| fail-on-error-status-code | When set to `true`, triggers [on-error](api-management-error-handling-policies.md) section for response codes in the range from 400 to 599 inclusive.  Policy expressions are not allowed.                                                                                                                                                                     | No       | `false`   |
+| buffer-response | Affects processing of chunked responses. When set to `false`, each chunk received from the backend is immediately returned to the caller. When set to `true`, chunks are buffered (8 KB, unless end of stream is detected) and only then returned to the caller.<br/><br/>Set to `false` with backends such as those implementing [server-sent events (SSE)](how-to-server-sent-events.md) that require content to be returned or streamed immediately to the caller. Policy expressions aren't allowed. | No | `true` |
+| fail-on-error-status-code | When set to `true`, triggers [on-error](api-management-error-handling-policies.md) section for response codes in the range from 400 to 599 inclusive.  Policy expressions aren't allowed.                                                                                                                                                                     | No       | `false`   |
 
 
 ## Usage

articles/api-management/include-fragment-policy.md

@@ -28,7 +28,7 @@ The policy inserts the policy fragment as-is at the location you select in the p
 
 | Attribute | Description                                                                                        | Required | Default |
 | --------- | -------------------------------------------------------------------------------------------------- | -------- | ------- |
-| fragment-id       | A string. Specifies the identifier (name) of a policy fragment created in the API Management instance. Policy expressions are not allowed. | Yes      | N/A     |
+| fragment-id       | A string. Specifies the identifier (name) of a policy fragment created in the API Management instance. Policy expressions aren't allowed. | Yes      | N/A     |
 
 ## Usage
 

articles/api-management/invoke-dapr-binding-policy.md

@@ -36,9 +36,9 @@ The policy assumes that Dapr runtime is running in a sidecar container in the sa
 | Attribute        | Description                     | Required | Default |
 |------------------|---------------------------------|----------|---------|
 | name            | Target binding name. Must match the name of the bindings [defined](https://github.com/dapr/docs/blob/master/daprdocs/content/en/reference/api/bindings_api.md#bindings-structure) in Dapr. Policy expressions are allowed.          | Yes      | N/A     |
-| operation       | Target operation name (binding specific). Maps to the [operation](https://github.com/dapr/docs/blob/master/daprdocs/content/en/reference/api/bindings_api.md#invoking-output-bindings) property in Dapr. Policy expressions are not allowed. | No | None |
-| ignore-error     | If set to `true` instructs the policy not to trigger ["on-error"](api-management-error-handling-policies.md) section upon receiving error from Dapr runtime. Policy expressions are not allowed. | No | `false` |
-| response-variable-name | Name of the [Variables](api-management-policy-expressions.md#ContextVariables) collection entry to use for storing response from Dapr runtime. Policy expressions are not allowed. | No | None |
+| operation       | Target operation name (binding specific). Maps to the [operation](https://github.com/dapr/docs/blob/master/daprdocs/content/en/reference/api/bindings_api.md#invoking-output-bindings) property in Dapr. Policy expressions aren't allowed. | No | None |
+| ignore-error     | If set to `true` instructs the policy not to trigger ["on-error"](api-management-error-handling-policies.md) section upon receiving error from Dapr runtime. Policy expressions aren't allowed. | No | `false` |
+| response-variable-name | Name of the [Variables](api-management-policy-expressions.md#ContextVariables) collection entry to use for storing response from Dapr runtime. Policy expressions aren't allowed. | No | None |
 | timeout | Time (in seconds) to wait for Dapr runtime to respond. Can range from 1 to 240 seconds. Policy expressions are allowed.| No | 5 |
 | template | Templating engine to use for transforming the message content. "Liquid" is the only supported value.  | No | None |
 | content-type | Type of the message content. "application/json" is the only supported value. | No | None |