text edits

Author: rosemarymarano

documentation/staging/content/navigate/kubernetes/k8s-ingress-controller.md

@@ -49,8 +49,7 @@ cluster attempts to pull the image and start the container.
 - The `Docker Registry Secret Name` field specifies the name of the Kubernetes pull secret to use when pulling the image.
 To create this secret, enable `Create Docker Hub Secret` and fill in the pull secret data in the `Docker Hub Username`, `Docker Hub Password`,
 and `Docker Hub Email Address` fields.
-- For NGINX ingress controller, if you desire to have SSL pass through ingress route, enable `
-  Allow SSL pass through to target service`.  
+- For the NGINX ingress controller, if you want to have SSL pass through the ingress route, enable `Allow SSL pass through to target service`.  
 
 #### TLS Secret for Ingress Routes
 Use this pane to configure the Transport Layer Security (TLS) secret containing the certificate and private key data that will be used by the
@@ -88,16 +87,17 @@ When editing a route:
 - Use the `Virtual Host` and `Path Expression` fields to define the matching rules that determine which requests match this route.  
 - All requests in the defined rules are routed to the service specified by the `Target Service` field that resides in the namespace specified by the read-only
 `Target Service Namespace` field and the port specified by the `Target Port` field.  
-- Specify transport option for the ingress route.
-    * Select `Plain HTTP` for unencrypted traffic from client through ingress controller to the target service
-    * Select `SSL terminate at ingress controller` for SSL 
-      terminating 
-      at ingress controller and then unencrypted traffic from ingress controller to target service.  Check `Is 
-      target service WebLogic Console?
-      ` if the target service is `WebLogic Console` service.  
-    * Select `SSL pass through` for SSL traffic pass through ingress 
-      controller and terminate at target service.  If you select this option, all SSL traffic from the `Virtual Host` 
-      will be routed to the target service.  Make sure the `Target Port` supports SSL.
+- Specify the `Transport Option` for the ingress route:
+    * Select `Plain HTTP` for unencrypted traffic from the client through the ingress controller to the target service.
+    * Select `SSL terminate at ingress controller` for SSL
+      terminating
+      at the ingress controller and then unencrypted traffic from the ingress controller to the target service.  
+      * Enable `Is target service WebLogic Console?` if the target service is the `WebLogic Console` service.  
+    * Select `SSL pass through` for SSL traffic to pass through the ingress
+      controller and then terminate at the target service.  
+      * If you select this option, then all SSL traffic from the `Virtual Host`
+      will be routed to the target service.  
+      * Make sure that the `Target Port` supports SSL.
 - Use the `Ingress Route Annotations` table to
 add annotations to the ingress route, as needed.  Do not remove any pre-populated annotations.