diff --git a/docs/custom-apps.md b/docs/custom-apps.md
index 1853c05c..a3d4ef6c 100644
--- a/docs/custom-apps.md
+++ b/docs/custom-apps.md
@@ -43,6 +43,7 @@ To verify the previous step, decode the APPS_JSON_BASE64 environment variable (w
 ```shell
 echo -n ${APPS_JSON_BASE64} | base64 -d > apps-test-output.json
 ```
+
 2. Open the apps-test-output.json file to review the JSON output and ensure that the content is correct.
 
 Note:
diff --git a/docs/error-nginx-entrypoint-windows.md b/docs/error-nginx-entrypoint-windows.md
index 2a1c5048..7be1c2ca 100644
--- a/docs/error-nginx-entrypoint-windows.md
+++ b/docs/error-nginx-entrypoint-windows.md
@@ -3,8 +3,10 @@
 If you're encountering the error `exec /usr/local/bin/nginx-entrypoint.sh: no such file or directory` in a Docker container on Windows, follow these steps to resolve the issue.
 
 ## 1. Check Line Endings
+
 On Windows, files often have `CRLF` line endings, while Linux systems expect `LF`. This can cause issues when executing shell scripts in Linux containers.
 
 - **Convert Line Endings using `dos2unix`:**
   ```bash
-  dos2unix resources/nginx-entrypoint.sh
\ No newline at end of file
+  dos2unix resources/nginx-entrypoint.sh
+  ```