Updated the co-pilot comments

Author: Prekshith-Microsoft

App/backend-api/Microsoft.GS.DPS.Host/appsettings.Development.json.sample

@@ -7,7 +7,8 @@
   },
   "AllowedHosts": "*",
   "ConnectionStrings": {
-    "AppConfig": "https://<app-config-name>.azconfig.io"  // Replace with the Azure App Configuration endpoint URL
+    // Replace with the Azure App Configuration endpoint URL
+    "AppConfig": "https://<app-config-name>.azconfig.io"
   }
 }
 

App/kernel-memory/service/Service/appsettings.Development.json.sample

@@ -1,6 +1,7 @@
 {
   "ConnectionStrings": {
-    "AppConfig": "https://<app-config-name>.azconfig.io"  // Replace with the Azure App Configuration endpoint URL
+    // Replace with the Azure App Configuration endpoint URL
+    "AppConfig": "https://<app-config-name>.azconfig.io"
   },
   "KernelMemory": {
     "Service": {

docs/LocalSetupGuide.md

@@ -77,7 +77,7 @@ APP_CONFIGURATION_URL=https://[Your app configuration service name].azconfig.io
 ```
 
 For reference, see the image below:
-![local_developement_setup_1](./images/local_development_setup_1.png)
+![local_development_setup_1](./images/local_development_setup_1.png)
 
 ### Required Azure RBAC Permissions
 
@@ -214,8 +214,8 @@ Copy-Item appsettings.Development.json.sample appsettings.Development.json   # W
 4. Edit the `appsettings.Development.json` file with your Azure App Configuration URL:
 
 ```json
+    // Replace with the Azure App Configuration endpoint URL
     "AppConfig": "https://<app-config-name>.azconfig.io"
-    // replace the app configuration name from the deployed resource group.
 ```
 #### Microsoft.GS.DPS Solution
 
@@ -234,8 +234,8 @@ Copy-Item appsettings.Development.json.sample appsettings.Development.json   # W
 4. Edit the `appsettings.Development.json` file with your Azure App Configuration URL:
 
 ```json
+    // Replace with the Azure App Configuration endpoint URL
     "AppConfig": "https://<app-config-name>.azconfig.io"
-    // replace the app configuration name from the deployed resource group.
 ```
 
 ---
@@ -393,4 +393,4 @@ 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..
+- [Quota Check](QuotaCheck.md) - Steps to verify Azure quotas and ensure required limits before deployment.

docs/PowershellSetup.md

@@ -24,17 +24,20 @@ This guide will help you add **PowerShell 7** (PowerShell Core) to your system
      C:\Program Files\PowerShell\7\
      ```
    - If the path is already there, you don't need to add it again.
+
 ### 4. Add PowerShell 7 Path
    - If the path is not already in the list, click **New** in the **Edit Environment Variable** window.
    - Add the following path to the list:
      ```
      C:\Program Files\PowerShell\7\
      ```
    > **Note:** If you installed PowerShell 7 in a custom location, replace the above path with the correct one.
+
 ### 5. Save Changes
    - After adding the path, click **OK** to close the **Edit Environment Variable** window.
    - Click **OK** again to close the **Environment Variables** window.
    - 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!