Fix billing images and formatting cleanup

Author: cindylay

docs/embedded/concepts/admin-exp/billing/billing.md

@@ -7,44 +7,54 @@ ms.localizationpriority: high
 
 # SharePoint Embedded billing
 
-SharePoint Embedded is a consumption-based Pay-as-you-go (PAYG) offering meaning you pay only for what you use. SharePoint Embedded provides two billing models which the tenant developing the SharePoint Embedded application can select for each specific container types, tailoring it to their unique business requirements. The two billing models are
+SharePoint Embedded is a consumption-based Pay-as-you-go (PAYG) offering meaning you pay only for what you use. SharePoint Embedded provides two billing models which the tenant developing the SharePoint Embedded application can select for respective container types, tailoring it to their unique business requirements. The two billing models are
 
-1) **Standard:** With this model, all consumption-based charges are directly billed to the tenant that owns/develops the application. Admin in the developer tenant  must establish a valid billing profile when creating a standard container type.
+### Standard
 
-<img width="800" alt="image" src="https://github.com/cindylay/sp-dev-docs/assets/132292644/53212756-569e-402c-8045-cb4d3bff4d50">
+With the standard billing model, all consumption-based charges are directly billed to the tenant that owns/develops the application. The admin in the developer tenant  must establish a valid billing profile when creating a standard container type.
+
+
+![Standard](../../../images/1bill521.png)
 
 
-**Pass-through (Coming Soon):** With this model, consumption-based charges are billed directly to the tenant registered to use the SharePoint Embedded application. Admin in the developer tenant don't need to set up a billing profile when creating a pass-through SharePoint Embedded container type. Once the container type is registered in the consuming tenant, the consuming tenant admin (SharePoint Admin or Global Admin) needs to set up the billing profile in the consuming tenant to use the SharePoint Embedded application.
+### Pass-through (Coming Soon) 
+
+With pass-through billing, consumption-based charges are billed directly to the tenant registered to use the SharePoint Embedded application. Admins in the developer tenant don't need to set up a billing profile when creating a pass-through SharePoint Embedded container type. Once the container type is registered in the consuming tenant, the consuming tenant admin (SharePoint Admin or Global Admin) needs to set up the billing profile in the consuming tenant to use the SharePoint Embedded application.
 
-<img width="800" alt="image" src="https://github.com/cindylay/sp-dev-docs/assets/132292644/c365892d-077c-4c71-9d94-1bfdccf26734">
+
+![Pass Through](../../../images/2bill521.png)
 
 
 ## Prerequisites to set up Pay-as-you-go for SharePoint Embedded
 
 To enable PAYG on SharePoint Embedded, you need:
 
 1. Existing SharePoint tenancy
-2. An Azure subscription in the tenancy
-3. A resource group attached to the Azure subscription
+1. An Azure subscription in the tenancy
+1. A resource group attached to the Azure subscription
+
 
 ### Roles and Permissions
 
 - Admin who sets up billing relationship for SharePoint Embedded needs to have owner or contributor permissions on Azure subscription.
 - Admin needs to have a SharePoint Embedded Administrator or Global Admin role to operate billing cmdlets.
 
+
 ## Set up a Standard Billing container type: 
 
 For standard billed container types, developer admin should set up billing in their tenant. Microsoft 365 SharePoint Embedded Administrator serves as the developer admin. Global Administrators in Microsoft 365 can assign users the SharePoint Embedded Administrator. The Global Administrator role already has all the permissions of the SharePoint Embedded Administrator role. A SharePoint Administrator can assign themselves the SharePoint Embedded Administrator role to act as a Developer Admin for SharePoint Embedded. The SharePoint Embedded Admin role is available in Microsoft Entra and Microsoft 365 Admin Center.
 
+
 Here are the step-by-step instructions on how to create a standard billing container: 
 
 1. Download and install the [latest version of SharePoint Online Management Shell](https://www.microsoft.com/download/details.aspx?id=35588)
-2. Open SharePoint Online Management Shell from **Start** screen, type **sharepoint**, and then select **SharePoint Online Management Shell**.
-3. Connect to SPO service using `Connect-SPOService` cmdlet by providing admin credentials associated with tenancy. For information on [how to use Connect-SPOService](/powershell/module/sharepoint-online/connect-sposervice), refer the linked documentation.
-4. Create container type using `New-SPOContainerType` cmdlet by providing an **azure subscription**, **resource group** associated with the subscription and a **region**.
+1. Open SharePoint Online Management Shell from **Start** screen, type **sharepoint**, and then select **SharePoint Online Management Shell**.
+1. Connect to SPO service using `Connect-SPOService` cmdlet by providing admin credentials associated with tenancy. For information on [how to use Connect-SPOService](/powershell/module/sharepoint-online/connect-sposervice), refer the linked documentation.
+1. Create container type using `New-SPOContainerType` cmdlet by providing an **azure subscription**, **resource group** associated with the subscription and a **region**.
 
    1. If you don't have an Azure subscription, you can create on by following steps here to [create an Azure subscription in your tenancy](/azure/cloud-adoption-framework/ready/azure-best-practices/initial-subscriptions)
-   2. If you don't have a resource group, you can create on by following steps here to [create a resource group](/azure/azure-resource-manager/management/manage-resource-groups-portal)
+   1. If you don't have a resource group, you can create on by following steps here to [create a resource group](/azure/azure-resource-manager/management/manage-resource-groups-portal)
+
 
 ```powershell
 New-SPOContainerType -ContainerTypeName <ContainerTypeName>
@@ -53,6 +63,7 @@ New-SPOContainerType -ContainerTypeName <ContainerTypeName>
                      -ResourceGroup <ResourceGroup>
                      -Region <Region>
 ```
+
 > [!IMPORTANT]
 > Every container type must have an owning application.
 > 
@@ -64,24 +75,25 @@ New-SPOContainerType -ContainerTypeName <ContainerTypeName>
 
 You can view properties of a container type and associated billing properties by using one of the two PowerShell cmdlets:
 
-1. To see all container types and billing properties except associated region:
+1. See all container types and billing properties except associated region:
 
     ```powershell
     Get-SPOContainerType
     ```
 
-1. To see billing properties associated with a container type including region:
+1. See billing properties associated with a container type including region:
 
     ```powershell
     Get-SPOContainerType -ContainerTypeId <ContainerTypeId>
     ```
 
-1. To update Azure subscription or resource group associated with a container type:
+1. Update Azure subscription or resource group associated with a container type:
 
     ```powershell
     Set-SPOContainerType -ContainerTypeId <ContainerTypeId> [-AzureSubscriptionId <AzureSubscriptionId>] [-ResourceGroup <ResourceGroup>]
     ```
 
-## SharePoint Embedded Meters
+## SharePoint Embedded meters
+
 Refer to the [SharePoint Embedded meters](docs/embedded/concepts/admin-exp/meters.md) article to learn more about the pay-as-you-go meters supported.