Fix the copilot review comments

Author: Prekshith-Microsoft

docs/DeleteResourceGroup.md

@@ -24,7 +24,7 @@ If your deployment fails and you need to clean up the resources manually, follow
 1. Click on the **resource group name** to open it.
 2. Click the **Delete resource group** button at the top.
 
-![Delete Resource Group](images/DeleteRG.png)
+![Delete Resource Group](images/delete-rg.png)
 
 3. Type the resource group name in the confirmation box and click **Delete**.
 
@@ -48,6 +48,4 @@ If you don’t want to delete the entire resource group, follow these steps:
 - After a few minutes, refresh the **Resource groups** page.
 - Ensure the deleted resource or group no longer appears.
 
-📌 **Tip:** If a resource fails to delete, check if it's **locked** under the **Locks** section and remove the lock.
-
-
+📌 **Tip:** If a resource fails to delete, check if it's **locked** under the **Locks** section and remove the lock.

docs/LocalSetupGuide.md

@@ -3,11 +3,10 @@
 This guide provides comprehensive instructions for setting up the Document Knowledge Mining Solution Accelerator for local development across Windows, Linux, and macOS platforms.
 
 ---
-## Step 1: Prerequisites - Install Required Tools
+## Step 1: Install Required Tools
 Install these tools before you start:
 - [Visual Studio](https://visualstudio.microsoft.com/)
 - [Visual Studio Code](https://code.visualstudio.com/)
-- [Node.js (LTS)](https://nodejs.org/en).
 
 ### Windows Development
 ```
@@ -209,9 +208,8 @@ After deploying the accelerator, the `appsettings.Development.json` file will be
 
 #### Server Not Responded Issues
 
-- While running the Kernel solution, if you encounter an error such as **“server not responded”** or **“server not found”**, it usually indicates that the required resource is not responding.  
+- While running the Kernel solution, if you encounter an error such as `server not responded` or `server not found`, it usually indicates that the required resource is not responding.   
 - Ensure that the necessary **Kubernetes services** are running. If not, start the Kubernetes service and then run the Kernel solution again.
-. 
 
 #### Permission Issues (Linux/macOS)
 
@@ -258,5 +256,5 @@ cat .env | grep -v '^#' | grep '='  # Should show key=value pairs
 
 - [Deployment Guide](DeploymentGuide.md) - Instructions for production deployment.
 - [Delete Resource Group](DeleteResourceGroup.md) - Steps to safely delete the Azure resource group created for the solution.
-- [Powershell Setup](PowershellSetup.md) - Instructions for setting up PowerShell and required scripts.
-- [Quota Check](QuotaCheck.md) - Steps to verify Azure quotas and ensure required limits before deployment.
+- [PowerShell Setup](PowershellSetup.md) - Instructions for setting up PowerShell and required scripts.
+- [Quota Check](QuotaCheck.md) - Steps to verify Azure quotas and ensure required limits before deployment..

docs/PowershellSetup.md

@@ -37,8 +37,7 @@ This guide will help you add **PowerShell 7** (PowerShell Core) to your system
    - Finally, click **OK** to exit the **System Properties** window.
 ### 6. Verify PowerShell 7 in PATH
    - Open **Command Prompt** or **Run** (press `Win + R`).
-   - Type `pwsh` and press Enter.
-   - If PowerShell 7 opens, you've successfully added it to your PATH!
+   - Type `pwsh` and press Enter. If PowerShell 7 opens, you've successfully added it to your PATH!
 ---
 ## Troubleshooting
 - **PowerShell 7 not opening:** Ensure the path to PowerShell 7 is entered correctly. If you're using a custom installation folder, check that the correct path is added to the `Path` variable.