Update native dev instructions

davidshq · Apr 10, 2023 · 96beb7c · 96beb7c
1 parent 949ee4e
commit 96beb7c
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/how-to/how-to-native-development.md b/how-to/how-to-native-development.md
@@ -1,8 +1,8 @@
 # Finding the Native Development Directions
 In the `dev` folder of MIQA one can find a `NATIVE.md` file which explains how to setup the application to perform local development.
 
-# Run Docker command from repo root, not dev folder
-In the `/dev/README.md` one is instructed to run the `docker-compose` command from within the `/dev` folder. When running the `NATIVE` configuration you'll need to use the `docker-compose.yml` file in the root of the repo. 
+# Run the Docker command from repo root, not the dev folder
+In the `/dev/README.md` one is instructed to run the `docker-compose` command from within the `/dev` folder. When running the `NATIVE` configuration you'll need to use the `docker-compose.yml` file in the root of the repo.
 
 # Running Native Development After Performing Standard Dev Environment Setup
 It's worth noting that this can also be run after doing a full setup (e.g. using `dev/README.md`). Ensure all the Docker containers have been shut down and then run the `docker-compose` command in `NATIVE.md`.
@@ -13,4 +13,4 @@ You can then proceed with the instructions under "Initial Setup" under `NATIVE.m
 Also note that it is possible to continue running the node.js frontend by starting up the `npm` container.
 
 # What is still running in Docker with native?
-By default MIQA will still use the `rabbitmq`, `minio`, and `postgres` containers. As noted above it is also possible to run the frontend using the `npm ` container if one has performed a full setup (e.g. using `dev/README.md`) previously.
+By default MIQA will still use the `rabbitmq`, `minio`, and `postgres` containers. As noted above it is also possible to run the frontend using the `npm ` container if one has performed a full setup (e.g. using `dev/README.md`) previously.