Merge pull request #3556 from dlabrecq/release3

Clean up docs
project-koku · Dec 7, 2023 · c66bceb · c66bceb
2 parents 59ef7a5 + 090cacf
commit c66bceb
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 5 deletions.
diff --git a/README.md b/README.md
@@ -73,9 +73,11 @@ make dev-static-node
 npm start:csb
 ```
 
-### Running Koku UI with a local Koku UI microfrontend (MFE)
+### Running Koku UI with a local Koku microfrontend (MFE)
 
-1. Start development server in Koku UI microfrontend (MFE) repo
+See https://github.com/project-koku/koku-ui-mfe
+
+1. Start development server in Koku microfrontend (MFE) repo
 ```
 npm start:static
 ```
@@ -85,16 +87,17 @@ npm start:static
 npm start:mfe
 ```
 
-### Running Koku UI with a local Koku UI microfrontend (MFE) and Cloud Services Backend
+### Running Koku UI with a local Koku microfrontend (MFE) and Cloud Services Backend
 
 See https://github.com/RedHatInsights/chrome-service-backend/blob/main/docs/cloud-services-config.md#serving-files-locally
+and https://github.com/project-koku/koku-ui-mfe
 
 1. Serve files locally from Cloud Services Backend repo
 ```
 make dev-static-node
 ```
 
-2. Start development server in Koku UI microfrontend (MFE) repo
+2. Start development server in Koku microfrontend (MFE) repo
 ```
 npm start:static
 ```

diff --git a/RELEASE.md b/RELEASE.md
@@ -1,6 +1,6 @@
 # Releasing Koku UI
 
-This doc describes how to release the UI to each staging environment. Note that this should be done in order for testing purposes; stage-stable, prod-beta, and finally prod-stable
+This doc describes how to release the Koku UI to each staging environment. Note that this should be done in order for testing purposes; stage-stable, prod-beta, and finally prod-stable
 
 ## Release script