Merge remote-tracking branch 'origin/cps-rm-local-build' into cps-rm-local-build

Author: Prajwal-Microsoft

docs/DeploymentGuide.md

@@ -180,7 +180,7 @@ Once you've opened the project in [Codespaces](#github-codespaces), [Dev Contain
 ## Post Deployment Steps
 1. Optional: Publishing Local Build Container to Azure Container Registry 
 
-If you need to rebuild the source code and push the updated container to the deployed Azure Container Registry, follow these steps:
+   If you need to rebuild the source code and push the updated container to the deployed Azure Container Registry, follow these steps:
 
    - **Linux/macOS**:
      ```bash
@@ -194,9 +194,9 @@ If you need to rebuild the source code and push the updated container to the dep
      .\docker-build.ps1
      ```
 
-This will create a new Azure Container Registry, rebuild the source code, package it into a container, and push it to the Container Registry created.
+    This will create a new Azure Container Registry, rebuild the source code, package it into a container, and push it to the Container Registry created.
 
-1. **Register Schema Files**
+2. **Register Schema Files**
 
      > Want to customize the schemas for your own documents? [Learn more about adding your own schemas here.](./CustomizeSchemaData.md)
 
@@ -226,7 +226,7 @@ This will create a new Azure Container Registry, rebuild the source code, packag
     - **Verify Results**
         ![schema file registration](./images/SchemaFileRegistration.png)  
 
-2. **Import Sample Data**  
+3. **Import Sample Data**  
     - Grab the Schema IDs for Invoice and Property Damage Claim Form's Schema from first step
     - Move to the folder location to samples in ContentProcessorApi - [/src/ContentProcessorApi/samples/](/src/ContentProcessorApi/samples/)
     - Execute the script with Schema IDs