Merge pull request #215421 from alexbuckgit/alexbuckgit/docutune-autopr-20221021-152746-3422572

Fix formatting issues

Author: prmerger-automator[bot]

articles/azure-functions/functions-bindings-storage-blob-trigger.md

@@ -23,10 +23,11 @@ There are several ways to execute your function code based on changes to blobs i
 | Filters | [Blob name pattern](#blob-name-patterns)  | [Event filters](../storage/blobs/storage-blob-event-overview.md#filtering-events) | n/a | [Event filters](../storage/blobs/storage-blob-event-overview.md#filtering-events) |
 | Requires [event subscription](../event-grid/concepts.md#event-subscriptions) | No | Yes | No | Yes |
 | Supports high-scale² | No | Yes | Yes | Yes |
-| Description | Default trigger behavior, which relies on polling the container for updates. For more information, see the [examples in this article](#example). | Consumes blob storage events from an event subscription. Requires a `Source` parameter value of `EventGrid`. For more information, see [Tutorial: Trigger Azure Functions on blob containers using an event subscription](./functions-event-grid-blob-trigger.md). | Blob name string is manually added to a storage queue when a blob is added to the container. This value is passed directly by a Queue Storage trigger to a Blob Storage input binding on the same function. | Provides the flexibility of triggering on events besides those coming from a storage container. Use when need to also have non-storage events trigger your function. For more information, see [How to work with Event Grid triggers and bindings in Azure Functions](event-grid-how-tos.md). | 
+| Description | Default trigger behavior, which relies on polling the container for updates. For more information, see the [examples in this article](#example). | Consumes blob storage events from an event subscription. Requires a `Source` parameter value of `EventGrid`. For more information, see [Tutorial: Trigger Azure Functions on blob containers using an event subscription](./functions-event-grid-blob-trigger.md). | Blob name string is manually added to a storage queue when a blob is added to the container. This value is passed directly by a Queue Storage trigger to a Blob Storage input binding on the same function. | Provides the flexibility of triggering on events besides those coming from a storage container. Use when need to also have non-storage events trigger your function. For more information, see [How to work with Event Grid triggers and bindings in Azure Functions](event-grid-how-tos.md). |
 
-¹Blob Storage input and output bindings support blob-only accounts.  
-²High scale can be loosely defined as containers that have more than 100,000 blobs in them or storage accounts that have more than 100 blob updates per second.
+<sup>1</sup> Blob Storage input and output bindings support blob-only accounts.
+
+<sup>2</sup> High scale can be loosely defined as containers that have more than 100,000 blobs in them or storage accounts that have more than 100 blob updates per second.
 
 For information on setup and configuration details, see the [overview](./functions-bindings-storage-blob.md). 
 

articles/azure-netapp-files/performance-linux-concurrency-session-slots.md

@@ -153,15 +153,15 @@ In NFSv4.1, sessions define the relationship between the client and the server.
 
 Although Linux clients default to 64 maximum requests per session, the value of `max_session_slots` is tunable.  A reboot is required for changes to take effect.  Use the `systool -v -m nfs` command to see the current maximum in use by the client.  For the command to work, at least one NFSv4.1 mount must be in place:
 
-```
+```shell
 $ systool -v -m nfs
 {
 Module = "nfs"
-…
+...
   Parameters:
-…
-    max_session_slots   = "64"   
-…
+...
+    max_session_slots   = "64"
+...
 }
 ```
 

articles/cost-management-billing/manage/ea-transfers.md

@@ -37,10 +37,7 @@ When you request an account transfer with a support request, provide the followi
 Other points to keep in mind before an account transfer:
 
 - Approval from a full EA Administrator, not a read-only EA administrator, is required for the target and source enrollment.
-    - If you have only UPN (User Principal Name) entities configured as full EA administrators without access to e-mail, you must perform one of the following actions:
-        - Create a temporary full EA administrator account in the EA portal  
-    — Or — 
-        - Provide EA portal screenshot evidence of a user account associated with the UPN account
+    - If you have only UPN (User Principal Name) entities configured as full EA administrators without access to e-mail, you must **either** create a temporary full EA administrator account in the EA portal **or** provide EA portal screenshot evidence of a user account associated with the UPN account.
 - You should consider an enrollment transfer if an account transfer doesn't meet your requirements.
 - Your account transfer moves all services and subscriptions related to the specific accounts.
 - Your transferred account appears inactive under the source enrollment and appears active under the target enrollment when the transfer is complete.

articles/cost-management-billing/manage/mca-setup-account.md

@@ -45,10 +45,9 @@ Before you start the setup, we recommend you do the following actions:
 
 ## Access required to complete the setup
 
-To complete the setup, you need the following access:
+To complete the setup, you need both of these roles:
 
-- Owner of the billing account that was created when the Microsoft Customer Agreement was signed. To learn more about billing accounts, see [Your billing account](../understand/mca-overview.md#your-billing-account).  
-— And —
+- Owner of the billing account that was created when the Microsoft Customer Agreement was signed. To learn more about billing accounts, see [Your billing account](../understand/mca-overview.md#your-billing-account).
 - Enterprise administrator on the enrollment that is renewed.
 
 ### Start migration and get permission needed to complete setup