Merge pull request MicrosoftDocs#28810 from changeworld/patch-3

Jak-MS · web-flow · commit 06bc1b4c5a71 · 2019-04-25T15:44:30.000-05:00
Change to not translate unique names
diff --git a/articles/api-management/api-management-error-handling-policies.md b/articles/api-management/api-management-error-handling-policies.md
@@ -73,15 +73,15 @@ The `on-error` policy section can be used at any scope. API publishers can confi
 
  When an error occurs and control jumps to the `on-error` policy section, the error is stored in  [context.LastError](api-management-policy-expressions.md#ContextVariables) property, which can be accessed by policies in the `on-error` section. LastError has the following properties.  
   
-| Name     | Type   | Description                                                                                               | Required |
-|----------|--------|-----------------------------------------------------------------------------------------------------------|----------|
-| Source   | string | Names the element where the error occurred. Could be either policy or a  built-in pipeline step name.     | Yes      |
-| Reason   | string | Machine-friendly error code, which could be used in error handling.                                       | No       |
-| Message  | string | Human-readable error description.                                                                         | Yes      |
-| Scope    | string | Name of the scope where the error occurred and could be one of "global", "product", "api", or "operation" | No       |
-| Section  | string | Section name where error occurred. Possible values: "inbound", "backend", "outbound", or "on-error".       | No       |
-| Path     | string | Specifies nested policy, for example "choose[3]/when[2]".                                                        | No       |
-| PolicyId | string | Value of the `id` attribute, if specified by the customer, on the policy where error occurred             | No       |
+| Name       | Type   | Description                                                                                               | Required |
+|------------|--------|-----------------------------------------------------------------------------------------------------------|----------|
+| `Source`   | string | Names the element where the error occurred. Could be either policy or a  built-in pipeline step name.     | Yes      |
+| `Reason`   | string | Machine-friendly error code, which could be used in error handling.                                       | No       |
+| `Message`  | string | Human-readable error description.                                                                         | Yes      |
+| `Scope`    | string | Name of the scope where the error occurred and could be one of "global", "product", "api", or "operation" | No       |
+| `Section`  | string | Section name where error occurred. Possible values: "inbound", "backend", "outbound", or "on-error".       | No       |
+| `Path`     | string | Specifies nested policy, for example "choose[3]/when[2]".                                                        | No       |
+| `PolicyId` | string | Value of the `id` attribute, if specified by the customer, on the policy where error occurred             | No       |
 
 > [!TIP]
 > You can access the status code through context.Response.StatusCode.  
@@ -177,4 +177,4 @@ For more information working with policies, see:
 + [Policies in API Management](api-management-howto-policies.md)
 + [Transform APIs](transform-api.md)
 + [Policy Reference](api-management-policy-reference.md) for a full list of policy statements and their settings
-+ [Policy samples](policy-samples.md)	
++ [Policy samples](policy-samples.md)	
