Skip to content

Commit 5b7cdc9

Browse files
committed
Update README.adoc
1 parent 4d00d42 commit 5b7cdc9

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

README.adoc

+4-4
Original file line numberDiff line numberDiff line change
@@ -148,7 +148,7 @@ ibmcloud plugin install kubernetes-service
148148
[role=command]
149149
include::{common-includes}/gitclone.adoc[]
150150

151-
// no "try what you'll build" section in this guide since it would be too long due to all setup the user will have to do.
151+
// no "try what you'll build" section in this guide because it would be too long due to all setup the user will have to do.
152152

153153
// =================================================================================================
154154
// Creating a Kubernetes cluster on IBM Cloud
@@ -472,7 +472,7 @@ The following table gives an overview for each of the parameters specified using
472472
| *Parameter* | *Description*
473473
| `image.repository` | The name of your Docker image including registry/repository prefix
474474
| `image.tag` | The tag for your Docker image
475-
| `image.pullSecret` | The image pull secret, since the container registry is private
475+
| `image.pullSecret` | The image pull secret, because the container registry is private
476476
| `service.name` | The name of the service
477477
| `service.port` | The port exposed by the service
478478
| `service.targetPort` | The port exposed by the pod
@@ -495,11 +495,11 @@ system-app-ibm-open-libe-84976bccfb-r22lj 1/1 Running 0 23s
495495

496496
=== Finding the microservice's IP address and ports
497497

498-
The service used to expose our deployments has a type of `NodePort`. This means you can
498+
The service used to expose your deployments has a type of `NodePort`. This means you can
499499
access these services from outside of your cluster via a specific port. In this case,
500500
since `nodePort` is not specified, the ports are randomized so you must obtain
501501
the ports before making requests to the services. You must also obtain the public IP address
502-
of our cluster. Note that there are other ways to expose your services such as using a
502+
of your cluster. Note that there are other ways to expose your services such as using a
503503
`LoadBalancer` service type or using an `Ingress`. In production, you would most likely
504504
use an `Ingress`.
505505

0 commit comments

Comments
 (0)