Update logic-apps-exception-handling.md

Author: SyntaxC4

articles/logic-apps/logic-apps-exception-handling.md

@@ -84,7 +84,7 @@ specify a retry policy, the action uses the default policy.
 
 | Value | Type | Description |
 |-------|------|-------------|
-| <*retry-policy-type*> | String | The retry policy type you want to use: "default", "none", "fixed", or "exponential" | 
+| <*retry-policy-type*> | String | The retry policy type you want to use: `default`, `none`, `fixed`, or `exponential` | 
 | <*retry-interval*> | String | The retry interval where the value must use [ISO 8601 format](https://en.wikipedia.org/wiki/ISO_8601#Combined_date_and_time_representations). The default minimum interval is `PT5S` and the maximum interval is `PT1D`. When you use the exponential interval policy, you can specify different minimum and maximum values. | 
 | <*retry-attempts*> | Integer | The number of retry attempts, which must be between 1 and 90 | 
 ||||
@@ -277,9 +277,9 @@ For limits on scopes, see [Limits and config](../logic-apps/logic-apps-limits-an
 Although catching failures from a scope is useful, 
 you might also want context to help you understand 
 exactly which actions failed plus any errors or status codes that were returned. 
-The "@result()" expression provides context about the result of all actions in a scope.
+The `@result()` expression provides context about the result of all actions in a scope.
 
-The "@result()" expression accepts a single parameter (the scope's name) 
+The `@result()` expression accepts a single parameter (the scope's name) 
 and returns an array of all the action results from within that scope. 
 These action objects include the same attributes as the **@actions()** object, 
 such as the action's start time, end time, status, inputs, correlation IDs, and outputs. 
@@ -338,9 +338,9 @@ for any actions that failed within the scope "My_Scope":
 Here's a detailed walkthrough that describes what happens in this example:
 
 1. To get the result from all actions inside "My_Scope", 
-the **Filter Array** action uses this filter expression: "@result('My_Scope')"
+the **Filter Array** action uses this filter expression: `@result('My_Scope')`
 
-2. The condition for **Filter Array** is any "@result()" 
+2. The condition for **Filter Array** is any `@result()` 
 item that has a status equal to **Failed**. 
 This condition filters the array that has all the action 
 results from "My_Scope" down to an array with only the failed action results.
@@ -356,8 +356,8 @@ action result that was previously filtered.
 4. Send an HTTP POST on the **For each** item response body, 
 which is the `@item()['outputs']['body']` expression. 
 
-   The "@result()" item shape is the same as the 
-   "@actions()" shape and can be parsed the same way.
+   The `@result()` item shape is the same as the 
+   `@actions()` shape and can be parsed the same way.
 
 5. Include two custom headers with the failed action name (`@item()['name']`) 
 and the failed run client tracking ID (`@item()['clientTrackingId']`).