some small fixes

acend · Aug 13, 2023 · 0a4f524 · 0a4f524
1 parent 1a9fb93
commit 0a4f524
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/content/en/docs/deployment-strategies/_index.md b/content/en/docs/deployment-strategies/_index.md
@@ -17,4 +17,4 @@ This [document](https://www.cncf.io/wp-content/uploads/2018/03/CNCF-Presentation
 
 ## {{% task %}} Apply deployment strategies
 
-Apply some deployment strategies to the example from [lab 5](../05).
+Apply some deployment strategies to the example from the [Scaling](../scaling).
diff --git a/content/en/docs/exposing-a-service/_index.md b/content/en/docs/exposing-a-service/_index.md
@@ -8,7 +8,7 @@ In this lab, we are going to make the freshly deployed application from the last
 
 ## {{% task %}} Create a ClusterIP Service
 
-The command `{{% param cliToolName %}} apply -f 03_deployment.yaml` from the last lab creates a Deployment but no Service. A {{% param distroName %}} Service is an abstract way to expose an application running on a set of Pods as a network service. For some parts of your application (for example, frontends) you may want to expose a Service to an external IP address which is outside your cluster.
+The command `{{% param cliToolName %}} apply -f deployment_example-web-go.yaml` from the last lab creates a Deployment but no Service. A {{% param distroName %}} Service is an abstract way to expose an application running on a set of Pods as a network service. For some parts of your application (for example, frontends) you may want to expose a Service to an external IP address which is outside your cluster.
 
 {{% param distroName %}} `ServiceTypes` allow you to specify what kind of Service you want. The default is `ClusterIP`.
 

diff --git a/content/en/docs/troubleshooting/_index.md b/content/en/docs/troubleshooting/_index.md
@@ -152,7 +152,7 @@ The parameter `-f` allows you to follow the log file (same as `tail -f`). With t
 When a Pod is in state `CrashLoopBackOff` it means that although multiple attempts have been made, no container inside the Pod could be started successfully. Now even though no container might be running at the moment the `{{% param cliToolName %}} logs` command is executed, there is a way to view the logs the application might have generated. This is achieved using the `-p` or `--previous` parameter.
 
 {{% alert title="Note" color="info" %}}
-This command will only work on pods that had container restarts. You can check the `RESTARTS` column in the `oc get pods` output if this is the case.
+This command will only work on pods that had container restarts. You can check the `RESTARTS` column in the `{{% param cliToolName %}} get pods` output if this is the case.
 {{% /alert %}}
 
 ```bash