Final tweaks pt2

Author: Fredwards

README.md

@@ -79,7 +79,7 @@ Signing Up
 Using the Query Tool
 <br>
 <br>
-<a href="#"><img src="./app/assets/query_tool.gif" alt="Query-Tool-Demo" title="Query-Tool-Demo" align="center" height="500" /></a></a>
+<a href="#"><img src="./app/assets/query_tool.gif" alt="Query-Tool-Demo" title="Query-Tool-Demo" align="center" height="475" /></a></a>
 
 #
 ###### Return to [Top](#chronos)
@@ -89,7 +89,7 @@ Using the Query Tool
 This is for the latest Chronos version **5.2 release and later**.
 
 - Stable release: 7.0.0
-- LTS release: 6.1.0
+- LTS release: 7.0.0
 
 ### Pre-Installation
 Make sure you're running version 14.16.1 of <a href="#"><img src="./app/assets/node-logo-color.png" alt="Node" title="Node" align="center" height="20" /></a></a>, which is the most recent LTS (long-term support) version. 

examples/docker/README.md

@@ -1,6 +1,6 @@
 ![Chronos logo](https://raw.githubusercontent.com/Chronos2-0/Chronos/master/app/assets/logo2.png)
 ## Microservices Architecture
-Microservices architecture for testing [Chronos](https://github.com/oslabs-beta/Chronos), a microservice communication and health visualizer.
+Microservices architecture for testing [Chronos](https://github.com/open-source-labs/Chronos), a microservice communication and health visualizer.
 
 ## Purpose and Design - with docker implemented to avoid having to run multiple services in multiple terminals
 This sample microservices architecture allows developers to explore the functionality of Chronos but with one docker compose command. This consists of four microservices, which are contained within the directories:

examples/gRPC/README.md

@@ -1,6 +1,6 @@
 ![Chronos logo](https://raw.githubusercontent.com/Chronos2-0/Chronos/master/app/assets/logo2.png)
 ## Microservices Architecture
-Microservices architecture for testing [Chronos](https://github.com/oslabs-beta/Chronos), a microservice communication and health visualizer.
+Microservices architecture for testing [Chronos](https://github.com/open-source-labs/Chronos), a microservice communication and health visualizer.
 
 ## Purpose and Design
 This sample microservices architecture allows developers to explore the functionality of Chronos with gRPC calls. It consists of 3 microservices, which are contained within the directories:

examples/microservices/README.md

@@ -22,14 +22,14 @@ On each microservice in example/microserivces, perform the following steps
     - ** Reverse Proxy .env file will only require CHRONOS_URI
 
 ```
-Microservice_URI = mongodb+srv://<username>:<password>@cluster0.o2hx5.mongodb.net/<dbname>?retryWrites=true&w=majority
+<Microservice_URI> = mongodb+srv://<username>:<password>@cluster0.o2hx5.mongodb.net/<dbname>?retryWrites=true&w=majority
 
 CHRONOS_URI = mongodb+srv://<username>:<password>@cluster0.o2hx5.mongodb.net/<dbname>?retryWrites=true&w=majority
 ```
   - In each Microservice Mode.js file import and set the Microservice_URI
 
 ```
-const myURI = process.env.Microservice_URI;
+const myURI = process.env.<Microservice_URI>;
 
 ```
 
@@ -55,7 +55,7 @@ chronos.use({
   - Head over to localhost:3000 to view reverse proxy acting as the frontend of this microservice example
   - Start adding data!
   - Run `npm install` in the Chronos root folder.
-  - Run `npm run both` to start Electron app
+  - Then, run `npm run both` in the Chronos root folder to start the Electron app
     - Add a new application in Chronos app dashboard.
     - The URI should be your CHRONOS_URI
 

examples/microservices/books/bookserver.js

@@ -15,9 +15,9 @@ const app = express();
 const bodyParser = require('body-parser');
 const controller = require('./BookController.js');
 
-// UNCOMMENT THE LINE BELOW IF YOU HAVE A SPECIFIED 'jmxuri' PROPERTY IN
+// UNCOMMENT THE LINE BELOW IF YOU HAVE A SPECIFIED A 'jmxuri' PROPERTY IN
 // YOUR 'chronos-config.js' FILE
-// hronos.kafka();
+// chronos.kafka();
 
 // UNCOMMENT THE LINE BELOW AND PASS IN YOUR CHOSEN ARGUMENTS
 // app.use('/', cmd.microCom('books', 'mongo', process.env.BOOK_URI, 'yes'));