clean up vi first steps (fixes #3476) (#3481)

Author: xyb994

pages/vi/vi-chat.md

@@ -4,13 +4,13 @@
 
 Our **Discord** server is a great place to learn, discuss, and collaborate with other members to build a better Open Learning Exchange platform. The chat lets OLE’s development team and interns communicate easily, and signup is through each member’s GitHub account.
 
-Communication is key in every collaborative project, and OLE is no different. 
+Communication is key in every collaborative project, and OLE is no different.
 
 ## Best Practices
 
-As you complete the [Virtual Intern First Steps](vi-first-steps.md) and the [Mobile Intern First Steps](pages/mi/mi-10-steps.md), we want you to keep us updated in the discord server. Generally, you should comment in the chat when you make an issue or pull request, and then link to it. Make a mention (@*name*) of someone when you comment on their issue/pull request, then link to it. For example:
+As you complete the [Virtual Intern First Steps](vi-first-steps.md) aornd the [Mobile Intern First Steps](pages/mi/mi-10-steps.md), we want you to keep us updated in the discord server. Generally, you should comment in the chat when you make an issue or pull request, and then link to it. Make a mention (@*name*) of someone when you comment on their issue/pull request, then link to it. For example:
 
-> Hey @dogi, just commented on your issue: [https://github.com/open-learning-exchange/open-learning-exchange.github.io/issues/15](https://github.com/open-learning-exchange/open-learning-exchange.github.io/issues/15)
+> @ssamikshaa, I just commented on your issue: <https://github.com/open-learning-exchange/open-learning-exchange.github.io/issues/3459#issuecomment-2433505911>
 
 This good etiquette helps streamline communication between internship candidates and staff members alike! Feel free to look through the chat for more examples.
 

pages/vi/vi-docker-development-tutorial.md

@@ -53,28 +53,42 @@ Next, run `ng version` to check your Angular CLI version, look for `Angular CLI:
 
 ## Container Setup
 
+### Linux
+
 1. Create a `planetdev` directory for the planet dev data:
-  - **Linux**:
-    ```bash
-    sudo mkdir -p /srv/planetdev && cd /srv/planetdev
-    ```
-  - **macOS/Windows**:
-    ```bash
-    mkdir -p ~/srv/planetdev && cd ~/srv/planetdev
-    ```
+
+  ```bash
+  sudo mkdir -p /srv/planetdev && cd /srv/planetdev
+  ```
+
 2. Download the development yml file:
-  - **Linux**:
-    ```bash
-    sudo wget https://raw.githubusercontent.com/ole-vi/planet-prod-configs/main/planet-dev.yml
-    ```
-  - **macOS/Windows**:
-    ```bash
-    curl https://gist.githubusercontent.com/xyb994/0d14dfe302df0df0d4e8d8df0d1d5feb/raw/planet-dev-mac.yml -o planet-dev.yml
-    ```
+
+  ```bash
+  sudo wget https://raw.githubusercontent.com/ole-vi/planet-prod-configs/main/planet-dev.yml
+  ```
+
 3. Start the containers: `sudo docker compose -f planet-dev.yml -p planet-dev up -d`
 4. After a minute, run `sudo docker ps -a` to verify that you have 2 runnning containers – `chatapi` and `couchdb`, the `db-init` container should have exited.
   - If `chatapi` service is restarting or exited, please ignore it for now as we are working on a fix
 
+### macOS/Windows
+
+1. Create a `planetdev` directory for the planet dev data:
+
+  ```bash
+  mkdir -p ~/srv/planetdev && cd ~/srv/planetdev
+  ```
+
+2. Download the development yml file:
+
+  ```bash
+  curl https://gist.githubusercontent.com/xyb994/0d14dfe302df0df0d4e8d8df0d1d5feb/raw/planet-dev-mac.yml -o planet-dev.yml
+  ```
+
+3. Start the containers: `docker compose -f planet-dev.yml -p planet-dev up -d`
+4. After a minute, run `docker ps -a` to verify that you have 2 runnning containers – `chatapi` and `couchdb`, the `db-init` container should have exited.
+  - If `chatapi` service is restarting or exited, please ignore it for now as we are working on a fix
+
 ## Configure CORS for CouchDB with add-cors-to-couchdb project:
 
 We use the [Add Cors to CouchDB](https://github.com/pouchdb/add-cors-to-couchdb) project to enable CORS on the CouchDB server. This is necessary for the Planet project to work correctly. We only need this for initialization purposes.
@@ -126,7 +140,6 @@ curl -X PUT http://localhost:2200/_node/nonode@nohost/_config/log/writer -d '"fi
 curl -X PUT http://localhost:2200/_node/nonode@nohost/_config/chttpd/authentication_handlers -d '"{chttpd_auth, cookie_authentication_handler}, {chttpd_auth, proxy_authentication_handler}, {chttpd_auth, default_authentication_handler}"'
 
 # run the couchdb-setup.sh script to set up the couchdb database for the planet project
-chmod +x couchdb-setup.sh
 bash couchdb-setup.sh -p 2200 -i
 ```
 

pages/vi/vi-docker-installation.md

@@ -62,7 +62,7 @@ docker tag treehouses/planet:chatapi treehouses/planet:chatapi-local
 
 # create a dedicated directory
 # for mapping Docker container volumes and saving configuration files
-sudo mkdir /srv/planet
+sudo mkdir -p /srv/planet
 cd /srv/planet
 
 # download production docker compose yml file and rename it

pages/vi/vi-docker-tutorial.md

@@ -20,7 +20,7 @@ Take the opportunity to read more about the tools and languages we use to deepen
 
 The MDwiki offers plenty of resources to help you complete these steps. You'll find a list of useful links at the end of each step. :)
 
-**We also would like you to keep us regularly updated in the Discord channel as you complete these steps. We will ask you to send messages, links, and screenshots along the way, which we'll use to track your progress. Please make sure not to miss this, as it's crucial for us to track your work.**
+**We also would like you to keep us regularly updated in our Discord server's `#vi-software` channel as you complete these steps. We will ask you to send messages, links, and screenshots along the way, which we'll use to track your progress. Please make sure not to miss this, as it's crucial for us to track your work.**
 
 A significant part of these steps is identifying problems or suggesting improvements for this MDwiki. As you complete the steps, take note of any issues you encounter or ideas for enhancements. This helps improve the MDwiki and these steps for future interns.