fix: Minor documentation updates; typos and other updates (aws-sample…

…s#1150) Co-authored-by: Niall Thomson <thomson.niall@gmail.com>
yunjianlu · Oct 28, 2024 · 444f2a2 · 444f2a2
1 parent f9e38d3
commit 444f2a2
Show file tree

Hide file tree

Showing 3 changed files with 5 additions and 5 deletions.
diff --git a/website/docs/introduction/getting-started/microservices.md b/website/docs/introduction/getting-started/microservices.md
@@ -19,4 +19,4 @@ Each of the components in the microservices architecture is conceptually similar
 
 ![Microservices in Kubernetes](./assets/microservices.webp)
 
-The **ui** component receives HTTP requests from, for example, a users browser. It then makes HTTP requests to other API components in the architecture to fulfill that request and returns a response to the user. Each of the downstream components may have their own data stores or other infrastructure. The Namespaces are a logical grouping of the resources for each microservice and also act as a soft isolation boundary, which can be used to effectively implement controls using Kubernetes RBAC and Network Policies.
+The **ui** component receives HTTP requests from, for example, a user's browser. It then makes HTTP requests to other API components in the architecture to fulfill that request and returns a response to the user. Each of the downstream components may have their own data stores or other infrastructure. The Namespaces are a logical grouping of the resources for each microservice and also act as a soft isolation boundary, which can be used to effectively implement controls using Kubernetes RBAC and Network Policies.
diff --git a/website/docs/introduction/helm/index.md b/website/docs/introduction/helm/index.md
@@ -46,12 +46,12 @@ $ helm repo add bitnami https://charts.bitnami.com/bitnami
 $ helm repo update
 ```
 
-Now we can search the repository for charts, for example the `postgresql` chart:
+Now we can search the repository for charts, for example the `nginx` chart:
 
 ```bash
-$ helm search repo postgresql
+$ helm search repo nginx
 NAME                    CHART VERSION   APP VERSION     DESCRIPTION
-bitnami/postgresql      X.X.X           X.X.X           PostgreSQL (Postgres) is an open source object-...
+bitnami/nginx           X.X.X           X.X.X           NGINX Open Source is a web server that can be a...
 [...]
 ```
 

diff --git a/website/docs/introduction/navigating-labs.md b/website/docs/introduction/navigating-labs.md
@@ -15,7 +15,7 @@ The content of this workshop is made up of:
 1. Individual lab exercises
 2. Supporting content that explains concepts related to the labs
 
-The lab exercises are designed in a way that you can run any modules as a self-container exercise. Lab exercises will be displayed in the sidebar to the left and are designated by the icon shown here:
+The lab exercises are designed in a way that you can run any modules as a self-contained exercise. Lab exercises will be displayed in the sidebar to the left and are designated by the icon shown here:
 
 ![Lab icon example](./assets/lab-icon.webp)
Original file line number	Diff line number	Diff line change
Expand Up		@@ -19,4 +19,4 @@ Each of the components in the microservices architecture is conceptually similar

		![Microservices in Kubernetes](./assets/microservices.webp)

		The ui component receives HTTP requests from, for example, a users browser. It then makes HTTP requests to other API components in the architecture to fulfill that request and returns a response to the user. Each of the downstream components may have their own data stores or other infrastructure. The Namespaces are a logical grouping of the resources for each microservice and also act as a soft isolation boundary, which can be used to effectively implement controls using Kubernetes RBAC and Network Policies.
		The ui component receives HTTP requests from, for example, a user's browser. It then makes HTTP requests to other API components in the architecture to fulfill that request and returns a response to the user. Each of the downstream components may have their own data stores or other infrastructure. The Namespaces are a logical grouping of the resources for each microservice and also act as a soft isolation boundary, which can be used to effectively implement controls using Kubernetes RBAC and Network Policies.