Formating md

Author: ragaumon

getting-started/docker-compose/README.md

@@ -236,18 +236,22 @@ You can quickly use the Zaken API by creating a sample case ("zaak") using Postm
 **Steps:**
 
 1. **Import the Create Case collection and environment**
+
    - Open Postman;
    - Go to the Collections tab. Import [ZGW Create Case.postman_collection.json](https://github.com/OneGround/ZGW-APIs-postman-tests/blob/main/ZGW%20Create%20Case.postman_collection.json);
    - Go to the Environments tab. Import [ZGW Create Case.environment.json](https://github.com/OneGround/ZGW-APIs-postman-tests/blob/main/ZGW%20Create%20Case.environment.json).
 
 2. **Obtain an Access Token**
+
    - Follow the instructions in the "Configure API Authentication" section above to get a valid access token.
    - Paste the token into the `jwt_token` variable in your Postman Create Case Environment.
 
 3. **Set Up Other Environment Variables**
+
    - Update the variables for your local setup if they deviate from standard set up, such as `zrc_url`.
 
 4. **Create a Sample Case**
+
    - In the imported collection `ZGW Create Case`, find the folder named `Casetype`. Click 'run' and 'Run ZGW Create Case'. The catalog will be created, a case and other types will be added.
    - Find the folder named `Case`. Click 'run' and 'Run ZGW Create Case'. The case with related entities (status, result, document) will be added. If you need more cases run it multiple times.
 
@@ -259,7 +263,6 @@ To stop all running Docker containers, run the following command from the `docke
 
 ```bash
 docker compose down
-
 ```
 
 ## Service Endpoints and Tools

getting-started/standalone/README.md

@@ -41,7 +41,7 @@ Before you begin, ensure you have the following components installed and running
 - A running **PostgreSQL** instance
 - A running **Redis** instance
 - An **OAuth2** compliant Identity Provider
-- A running **RabbitMQ** instance (_only required for the Notificaties API or if using the event bus for notifications_)
+- A running **RabbitMQ** instance (*only required for the Notificaties API or if using the event bus for notifications*)
 
 > **Note:** Not all APIs require every component. See the [API-Specific Configuration](#api-specific-configuration) section for the exact prerequisites for each service.
 
@@ -438,8 +438,6 @@ Logging__LogLevel__Default=Warning
 
 ---
 
----
-
 ## License
 
 This project is licensed under the [**BSD 3-Clause License**](https://github.com/OneGround/ZGW-APIs/blob/main/LICENSE).

localdev/README.md

@@ -82,6 +82,7 @@ Follow the steps for your operating system.
 #### For Windows (using PowerShell)
 
 1. **Open PowerShell as an Administrator.**
+
      - Click the Start menu, type "PowerShell", right-click on "Windows PowerShell", and select "Run as administrator".
 
 2. **Navigate to the certificate installer directory:**
@@ -108,7 +109,7 @@ Follow the steps for your operating system.
     .\install-oneground-certificate.ps1 -RelativeCertPath "..\..\localdev\oneground-certificates\oneground.local.pem"
     ```
 
-The script will import the certificate into the Windows "Trusted Root Certification Authorities" store.
+    The script will import the certificate into the Windows "Trusted Root Certification Authorities" store.
 
 #### For macOS and Linux (using Bash)
 
@@ -131,7 +132,7 @@ The script will import the certificate into the Windows "Trusted Root Certificat
     ./install-oneground-certificate.sh ../../oneground-certificates/oneground.local.pem
     ```
 
-This script installs the certificate into your system's keychain or trust store.
+    This script installs the certificate into your system's keychain or trust store.
 
 > **Note:** After installing the certificate, we recommend restarting your web browser to ensure the changes take effect.
 
@@ -140,6 +141,7 @@ This script installs the certificate into your system's keychain or trust store.
 To ensure all services can communicate with each other and are accessible in your browser, you need to map the service hostnames to your local machine. This is a crucial step for the local domain names (e.g., `zaken.oneground.local`) to work correctly.
 
 1. Open your `hosts` file as an administrator.
+
    - **Windows:** `C:\Windows\System32\drivers\etc\hosts`
    - **macOS/Linux:** `/etc/hosts`