diff --git a/content/en/docs/ibm/deploy/authentication.md b/content/en/docs/ibm/deploy/authentication.md
index d658244b8c61d12c3a7c2f308e325930b44141c1..03dfdb385e046eb995d68f6925b62c9d7f501f34 100644
--- a/content/en/docs/ibm/deploy/authentication.md
+++ b/content/en/docs/ibm/deploy/authentication.md
@@ -24,13 +24,13 @@ guide.
 
 ## Setting up an NLB
 
-To set up an NLB for your Kuberetes cluster, follow the official 
+To set up an NLB for your Kubernetes cluster, follow the official 
 [Classic: Setting up basic load balancing with an NLB 1.0](https://cloud.ibm.com/docs/containers?topic=containers-loadbalancer) 
 guide. Notice that the setup process for a multi-zone cluster differs from that 
 of a single-zone cluster. For details, go to 
 [Setting up an NLB 1.0 in a multi-zone cluster](https://cloud.ibm.com/docs/containers?topic=containers-loadbalancer#multi_zone_config).
 
-1. To use the exisitng Istio ingress gateway (instead of creating a new 
+1. To use the existing Istio ingress gateway (instead of creating a new 
 service), you need to update the service type of `istio-ingressgateway` to 
 `LoadBalancer` from `NodePort`. Run the following command:
 
diff --git a/content/en/docs/ibm/pipelines.md b/content/en/docs/ibm/pipelines.md
index 2495617fbc9fea5d70da2b6a8eb7dc216e22b645..091b1cb2b03e366fc6178cca934f67d0b86f78ee 100644
--- a/content/en/docs/ibm/pipelines.md
+++ b/content/en/docs/ibm/pipelines.md
@@ -1,6 +1,6 @@
 +++
 title = "Pipelines on IBM Cloud Kubernetes Service (IKS)"
-description = "Instructions for using Kubeflow Pipelines on IBM Cloud Kubernetes Servuce (IKS)"
+description = "Instructions for using Kubeflow Pipelines on IBM Cloud Kubernetes Service (IKS)"
 weight = 50
 +++
 
@@ -16,7 +16,7 @@ It requires authentication via the public endpoint of Kubeflow deployment when u
 1. `SESSION_COOKIE` - A session cookie starts with `authservice_session=`. You can obtain it from your browser after authenticated from Kubeflow UI. Notice that this session cookie expires in 24 hours, so you need to obtain it again after cookie expired.
 1. `KUBEFLOW_PROFILE_NAME` - Your Kubeflow profile name
 
-Once you obtain above information, it can use the following Python code to list all your Piplines experiments:
+Once you obtain above information, it can use the following Python code to list all your Pipelines experiments:
 ```Python
 import kfp
 
@@ -33,4 +33,4 @@ client = kfp.Client(
 experiments = client.list_experiments(namespace=KUBEFLOW_PROFILE_NAME)
 ```
 
-Pipelines components like experiments and runs are isolated by Kubeflow profiles. A Kubeflow user can only see Pipelines experiments and runs belonging to this user's Kubeflow profile.
\ No newline at end of file
+Pipelines components like experiments and runs are isolated by Kubeflow profiles. A Kubeflow user can only see Pipelines experiments and runs belonging to this user's Kubeflow profile.
diff --git a/content/en/docs/ibm/using-icr.md b/content/en/docs/ibm/using-icr.md
index af751c6d94e8528956c7857cda5636d681f8e249..8c4c4eb4cc06cbd7ee5d5bbdd833d7917e949284 100644
--- a/content/en/docs/ibm/using-icr.md
+++ b/content/en/docs/ibm/using-icr.md
@@ -35,7 +35,7 @@ See details and FAQs from the official guide [Setting up an image registry](http
 You will need an IBM Cloud IAM API Key to work with ICR if you:
 1. Have no access to the default image pull secret `all-icr-io` from the `default` namespace.
 2. Need to access container images in other IBM Cloud accounts.
-3. Need customized IAM policy by using a separate IAM sevice ID.
+3. Need customized IAM policy by using a separate IAM service ID.
 
 If you don't have an IBM Cloud IAM API Key, follow the official guide [Create an API Key](https://cloud.ibm.com/docs/account?topic=account-userapikey#create_user_key).