edited README files for gRPC, kubernetes, and npm package - removed repeated or unclear instructions

Author: beezoo10

chronos_npm_package/README.md

@@ -89,7 +89,7 @@ _See mode-specific configuration descriptions in the "Chronos Tracker for Micros
 
 The `microservice` property takes in a string. This should be a descriptive name for your microservice.
 
-- <img src="assets/important.png" alt="Important" title="Important" align="center" height="20" /> For **Dockerized** microservices, this field **must** match the _container_name_ of the corresponding Docker container.
+- <img src="../assets/important.png" alt="Important" title="Important" align="center" height="20" /> For **Dockerized** microservices, this field **must** match the _container_name_ of the corresponding Docker container.
 
 The `interval` property is optional and takes in an integer. This controls the Chronos monitoring frequency. If this is omitted, Chronos will default to recording server health every 60000 ms or 60 seconds.
 
@@ -279,7 +279,7 @@ When viewing your information in the Chronos Electron application the data will
 
 ### Chronos Tracker for gRPC
 
-To monitory your gRPC server, setup `chronos-config.js` as if it was a standard microservices example, but be sure to set the `connection` type to `gRPC`.
+To monitor your gRPC server, setup `chronos-config.js` as if it was a standard microservices example, but be sure to set the `connection` type to `gRPC`.
 
 ```js
 module.exports = {

examples/gRPC/README.md

@@ -1,5 +1,3 @@
-![Chronos logo](https://raw.githubusercontent.com/Chronos2-0/Chronos/master/app/assets/logo2.png)
-
 ## Microservices Architecture
 Microservices architecture for testing [Chronos](https://github.com/open-source-labs/Chronos), a microservice communication and health visualizer.
 
@@ -13,11 +11,12 @@ Each microservice has its own server, which receives requests from both the clie
 
 ## Getting Started w/ gRPC Example Microservices 
 
-Follow **'main'** branch README steps: Pre-Installation, Install Dependencies before start. 
+Follow **'main'** branch [README](../../README.md) steps: Pre-Installation, Install Dependencies before start. 
+
+We have already initialized Chronos within this example. To track gRPCs within your own application, please review the [README for the Chronos microtracker npm package](../../chronos_npm_package/README.md) for more information.
 
-On each microservice in example/microservices, perform the following steps
-  - **NOTE: Do this for microservices: books, orders, & reverse proxy**
-  - Create a .env file under each microservice folder and input your own Mongodb Atlas URI for Microservice_URI, CHRONOS_URI and ORDER_URI, see example below:
+On **each** microservice in ```example/microservices```, perform the following steps:
+  - Create a .env file under the microservice's folder and input your own Mongodb Atlas URI for Microservice_URI, CHRONOS_URI and ORDER_URI (example below):
 
 ```
 BOOK_URI = mongodb+srv://<username>:<password>@cluster0.o2hx5.mongodb.net/<dbname>?retryWrites=true&w=majority
@@ -26,34 +25,32 @@ CHRONOS_URI = mongodb+srv://<username>:<password>@cluster0.o2hx5.mongodb.net/<db
 
 ORDER_URI = mongodb+srv://<username>:<password>@cluster0.o2hx5.mongodb.net/<dbname>?retryWrites=true&w=majority
 ```
-  - In each Microservices *chronos-config.js* file, verify that `"mode"` property has a value of `"microservices"`
 
+  - In each Microservices *chronos-config.js* file, verify that `"mode"` property has a value of `"microservices"`
 
-  - ** Note: The Initialize Chronos step is already taken care of for you. 
   - Inside each microservice directory, install all dependencies using the `npm install`
   - Run `npm run start` in each folder directory
-  - Head over to localhost:3000 to view reverse proxy acting as the frontend of this microservice example
+  - Head over to localhost:3000 to view reverse proxy acting as the front end of this microservice example
 
 <p align="center">
   <img alt="gRPC reverse proxy front end" src="../../assets/gRPC_example_reverseProxy.png">
 </p>
 
   - Start adding data!
-  - Run `npm run both` to start Electron app
+  - Run `npm run dev:app` and `npm run dev:electron` **in separate terminals** to start Electron app
     - Add a new application in Chronos app dashboard.
     - The URI should be your CHRONOS_URI
 
 
-**To test the functionality of Chronos using this sample microservices architecture, you must have the [Chronos node module](https://www.npmjs.com/package/chronos-microservice-debugger3) within each microservice.**
-
- This is already included as a dependency therefore there should be no need to install it manually. But if it is missing from the dependency list, the installation instructions for both the Chronos node module and the Chronos desktop visualizer are below:
+**To test the functionality of Chronos using this sample microservices architecture, you must have the [Chronos microservice tracker](https://www.npmjs.com/package/@chronosmicro/tracker) within each microservice.**
 
+ This is already included as a dependency, therefore there should be no need to install it manually. But if it is missing from the dependency list, the installation instructions for both the Chronos node module and the Chronos desktop visualizer are below:
 
 #### Electron desktop application
 
 After installing the node module in each microservice, download the Electron desktop application from the public [Chronos](https://github.com/oslabs-beta/Chronos) repo.
 
-Inside the downloaded directory, install all dependencies using the `npm install` command followed by the `npm run both` command to start the Electron desktop application.
+Inside the downloaded directory, install all dependencies using the `npm install` command, followed by the `npm run both` command to start the Electron desktop application.
 
 ## Contributing
 
@@ -67,3 +64,4 @@ Chronos hopes to inspire an active community of both users and developers. For q
 [npm-url]: https://www.npmjs.com/package/chronos-microservice-debugger3
 [downloads-image]: https://img.shields.io/npm/dm/chronos-microservice-debugger3.svg
 [downloads-url]: https://npmjs.org/package/chronos-microservice-debugger3
+ 

examples/kubernetes/README.md

@@ -7,13 +7,13 @@ This example demonstrates how `Chronos` can be used to track health metrics of a
 - *scripts*: Scripts to automate some of the steps involved in running the example
 
 ## Install Docker Desktop
-This example has been developed and tested using the Kubernetes Engine packaged in the Docker Desktop application. Follow instructions online to download/install Docker Desktop and to enable the Kubernetes Engine.
+This example has been developed and tested using the Kubernetes Engine packaged in the Docker Desktop application. 
 
+Follow instructions online to download/install Docker Desktop and to **enable the Kubernetes Engine**. The examples will not work without the Kubernetes Engine enabled. 
 ## Build the Client
 `cd` into the *client* folder and run the following command:
 ```
 docker build -t frontend:1.0 .
-
 ```
 **Mac Users:** Alternatively running the above command, `cd` into the scripts folder and run the `buildClient.sh` script