Introduced some additional documentation refactoring.

Author: Wael Kdouh

docs/aca/01-deploy-api-to-aca/index.md

@@ -119,7 +119,7 @@ We will be using Azure CLI to deploy the Web API Backend to ACA as shown in the
     --sku Basic `
     --admin-enabled true
     ```
-???+ note
+!!! note
     Notice that we create the registry with admin rights `--admin-enabled` flag set to `true` which is not suited for real production, but good for our workshop.
 
 - Create an Azure Log Analytics Workspace which will provide a common place to store the system and application log data from all container apps running in the environment. Each environment should have its own Log Analytics Workspace. To create it, run the command below:

docs/aca/03-aca-dapr-integration/index.md

@@ -182,7 +182,7 @@ The SDK offers developers three ways of making remote service invocation calls:
  Notice how we assigned the Dapr App Id “tasksmanager-frontend-webapp” to the Frontend WebApp.
 
 !!! note
-    If you need to run both microservices together, you need to keep calling `dapr run` manually each time in the terminal. And when you have multiple microservices talking to each other you need to run at the same time to debug the solution. This can be a convoluted process. You can refer to the [debug and launch Dapr applications in VSCode](../../aca/20-appendix/01-run-debug-dapr-app-vscode.md) to see how to configure VScode for running and debugging Dapr applications.
+    If you need to run both microservices together, you need to keep calling `dapr run` manually each time in the terminal. And when you have multiple microservices talking to each other you need to run at the same time to debug the solution. This can be a convoluted process. You can refer to the [debug and launch Dapr applications in VSCode](../../aca/12-appendix/01-run-debug-dapr-app-vscode.md) to see how to configure VScode for running and debugging Dapr applications.
 
 !!! success
     Now both Applications are running using Dapr sidecar. Open your browser and browse for `https://localhost:{localwebappport}`. E.g. `https://localhost:7000` and provide an email to load the tasks for the user (e.g. tjoudeh@bitoftech.net).

docs/aca/04-aca-dapr-stateapi/index.md

@@ -256,7 +256,7 @@ To add the component file state store, add a new folder named **components** und
 
 Now you should be ready to launch both applications and start doing CRUD operations from the Frontend Web App including querying the store. All your data will be stored in Cosmos DB Database you just provisioned. 
 
-If you have been running the different microservices using the [debug and launch Dapr applications in VSCode](../../aca/20-appendix/01-run-debug-dapr-app-vscode.md) then remember to uncomment the following line inside tasks.json file. 
+If you have been running the different microservices using the [debug and launch Dapr applications in VSCode](../../aca/12-appendix/01-run-debug-dapr-app-vscode.md) then remember to uncomment the following line inside tasks.json file. 
 This will instruct dapr to load the local projects components [./components](.) instead of the global components' folder.
 
 ```json hl_lines="2"

docs/aca/05-aca-dapr-pubsubapi/index.md

@@ -39,7 +39,7 @@ We want to have more control and provide our own component file, so let's create
     --8<-- "docs/aca/05-aca-dapr-pubsubapi/dapr-pubsub-redis.yaml"
     ```
 
-To try out the Pub/Sub API, run the Backend API from VS Code by running the below command or using the Run and Debug tasks we have created in the appendix [post](../../aca/20-appendix/01-run-debug-dapr-app-vscode.md). 
+To try out the Pub/Sub API, run the Backend API from VS Code by running the below command or using the Run and Debug tasks we have created in the [appendix](../../aca/12-appendix/01-run-debug-dapr-app-vscode.md). 
 
 !!! note
     Don't forget to include the property `--resources-path`.  Remember to replace the placeholders with your own values
@@ -263,7 +263,7 @@ in the terminal to indicate the processing of the message.
 
 #### 6. Optional: Update VS Code Tasks and Launch Configuration Files
 
-If you have followed the steps in the [appendix](../../aca/20-appendix/01-run-debug-dapr-app-vscode.md) so far in order to be able to run the three services together (frontend, backend api, and backend processor) 
+If you have followed the steps in the [appendix](../../aca/12-appendix/01-run-debug-dapr-app-vscode.md) so far in order to be able to run the three services together (frontend, backend api, and backend processor) 
 and debug them in VS Code, we need to update the files `tasks.json` and `launch.json` to include the new service we have added. 
 
 ??? example "Click to expand the files to update"

docs/aca/06-aca-dapr-bindingsapi/index.md

@@ -188,7 +188,7 @@ Update and replace the code in the file with the code below. Pay close attention
 #### 6. Test Dapr Bindings Locally
 
 Now we are ready to give it an end-to-end test on our dev machines. Run the 3 applications together using Debug and Run button from VS Code. You can read how we configured the 3 apps to run together 
-in this [section](../../aca/20-appendix/01-run-debug-dapr-app-vscode.md).
+in this [section](../../aca/12-appendix/01-run-debug-dapr-app-vscode.md).
 
 Open Azure Storage Explorer on your local machine. If you don't have it installed you can install it from [here](https://azure.microsoft.com/en-us/products/storage/storage-explorer/#overview). 
 Login to your Azure Subscription and navigate to the storage account already created, create a queue, and use the same name you already used in the Dapr Input configuration file.

…/10-contributing/1-contribution-guide.md …/11-contributing/1-contribution-guide.mddocs/aca/10-contributing/1-contribution-guide.md renamed to docs/aca/11-contributing/1-contribution-guide.md docs/aca/10-contributing/1-contribution-guide.md renamed to docs/aca/11-contributing/1-contribution-guide.md

@@ -4,7 +4,6 @@ If you'd like to contribute to this guide, please read the following guidelines.
 
 - [Submit an issue or suggestion](2-Submit-issue-suggestion.md)
 - [Minor update or fix to an existing challenge and adding a new challenge](3-minor-update-fix.md)
-- [Run the github page locally with GitHub Codespaces](4-github-local-codespaces.md)
 
 # Contributing
 

…ontributing/2-Submit-issue-suggestion.md …ontributing/2-Submit-issue-suggestion.mddocs/aca/10-contributing/2-Submit-issue-suggestion.md renamed to docs/aca/11-contributing/2-Submit-issue-suggestion.md docs/aca/10-contributing/2-Submit-issue-suggestion.md renamed to docs/aca/11-contributing/2-Submit-issue-suggestion.md

@@ -25,7 +25,7 @@ To accomplish this, open file `launch.json` and add the two configurations shown
 === "launch.json"
 
     ```json
-    --8<-- "docs/aca/20-appendix/launch.json"
+    --8<-- "docs/aca/12-appendix/launch.json"
     ```
 !!! note 
     We have a `preLaunchTask` and a `postDebugTask` which we need to define right now. Those tasks are Dapr tasks.
@@ -44,7 +44,7 @@ Now we will add 4 tasks, for each application, there will be a task to support t
 === "tasks.json"
 
     ```json
-    --8<-- "docs/aca/20-appendix/tasks.json"
+    --8<-- "docs/aca/12-appendix/tasks.json"
     ```
 
 ??? tip "Curious to learn more about the tasks.json file above?"