edits (#3545)

Author: rosemarymarano

documentation/staging/content/managing-domains/accessing-the-domain/port-forward.md

@@ -3,7 +3,7 @@ title: "Use port forwarding"
 date: 2019-02-23T17:39:15-05:00
 draft: false
 weight: 3
-description: "Use port forwarding to access WebLogic Server Administration Consoles and WLST."
+description: "Use port forwarding to access WebLogic Server administration consoles and WLST."
 ---
 
 {{< table_of_contents >}}
@@ -21,7 +21,7 @@ from a private local network without exposing WebLogic's ports to a public netwo
 
 Here are the steps:
 
-1. Set up [WebLogic Administration Server network channels for port forward access](#set-up-administration-server-network-channels-for-port-forward-access).
+1. Set up [Administration Server network channels for port forward access](#set-up-administration-server-network-channels-for-port-forward-access).
 1. If you are setting up WLST access
 and your port forwarding local port is not going to be the same as the
 port number on the WebLogic Administration Server Pod,
@@ -129,7 +129,7 @@ When one or more custom administration channels are configured | internal-admin$
 ### Port forward to an Administration Server Pod    
 
 If you have
-[set up WebLogic Administration Server network channels for port forward access](#set-up-administration-server-network-channels-for-port-forward-access),
+[set up Administration Server network channels for port forward access](#set-up-administration-server-network-channels-for-port-forward-access),
 then you can run a `kubectl port-forward` command to access such a channel. The command:
 * By default, opens a port of your choosing on `localhost`
   on the machine where you run the command.
@@ -164,7 +164,7 @@ For example, if you have a WebLogic domain with:
 * An Administration Server named `admin-server` listening on non-SSL listen port `7001`
 * No administration port or administration channels configured on the Administration Server
 
-And, you have [set up WebLogic Administration Server network channels for port forward access](#set-up-administration-server-network-channels-for-port-forward-access) for this domain,
+And, you have [set up Administration Server network channels for port forward access](#set-up-administration-server-network-channels-for-port-forward-access) for this domain,
 then you can run either of the following commands to forward local port `32015` to
 the Administration Server Pod:
 

documentation/staging/content/managing-domains/accessing-the-domain/remote-admin-console.md

@@ -26,7 +26,7 @@ along with the URL of the WebLogic Server Administration Server's administration
 
 **Notes:**  
   * An Administration Server administration port typically is the same as its default port unless either an SSL port or an administration port is configured and enabled.
-  * If your domain home type is either [Domain in Image]({{< relref "/samples/domains/domain-home-in-image/_index.md" >}}) or [Model in Image]({{< relref "/samples/domains/model-in-image/_index.md" >}}), then do not use the WebLogic Remote Console to make changes to the WebLogic domain configuration as these changes are ephemeral and will be lost when servers restart. See [Choose a domain home source type]({{< relref "/managing-domains/choosing-a-model/_index.md" >}}).
+  * If your domain home type is either [Domain in Image]({{< relref "/samples/domains/domain-home-in-image/_index.md" >}}) or [Model in Image]({{< relref "/samples/domains/model-in-image/_index.md" >}}), then do not use the WebLogic Remote Console to make changes to the WebLogic domain configuration because these changes are ephemeral and will be lost when servers restart. See [Choose a domain home source type]({{< relref "/managing-domains/choosing-a-model/_index.md" >}}).
 
 
 {{% notice warning %}}
@@ -119,7 +119,7 @@ see [Use a `NodePort` for WLST]({{< relref "/managing-domains/accessing-the-doma
    Administration Server Pod according to these
    [instructions]({{< relref "/managing-domains/accessing-the-domain/port-forward.md" >}}).
 
-   **NOTE:** If you plan to run the Remote Console 
+   **NOTE:** If you plan to run the Remote Console
    on a different machine than the port forwarding command,
    then the port forwarding command needs to specify a `--address` parameter
    with the IP address of the machine that is hosting the command.

documentation/staging/content/managing-domains/accessing-the-domain/weblogic-admin-console.md

@@ -3,7 +3,7 @@ title: "Use the Administration Console"
 date: 2019-02-23T17:39:15-05:00
 draft: false
 weight: 1
-description: "Use the WebLogic Administration Console with domains running in Kubernetes."
+description: "Use the WebLogic Server Administration Console with domains running in Kubernetes."
 ---
 
 {{< table_of_contents >}}
@@ -13,17 +13,17 @@ You can access the WebLogic Server Administration Console external to the Kubern
 
    * [Use a load balancer](#use-a-load-balancer)
 
-   * Use an [Administration Server `NodePort`](#use-an-administration-server-nodeport).
+   * Use an [Administration Server `NodePort`](#use-an-administration-server-nodeport)
 
-   * [Use a `kubectl port-forward` connection](#use-a-kubectl-port-forward-connection).
+   * [Use a `kubectl port-forward` connection](#use-a-kubectl-port-forward-connection)
 
 **Notes:**
- * For production use cases, Oracle recommends using a load balancer with ingress path routing rules and an SSL port to access the WebLogic Server Administration Console. 
+ * For production use cases, Oracle recommends using a load balancer with ingress path routing rules and an SSL port to access the WebLogic Server Administration Console.
 
- * To verify that your load balancer, NodePort, or kubectl port-forward setup is working as expected, see [Test]({{< relref "#test" >}}).
+ * To verify that your load balancer, NodePort, or `kubectl port-forward` setup is working as expected, see [Test]({{< relref "#test" >}}).
 
- * Do not use the WebLogic Server Administration Console to start or stop servers, or for scaling clusters. See [Starting and stopping servers]({{< relref "/managing-domains/domain-lifecycle/startup#starting-and-stopping-servers" >}}) and [Scaling]({{< relref "/managing-domains/domain-lifecycle/scaling.md" >}}). 
- * If your domain home type is either [Domain in Image]({{< relref "/samples/domains/domain-home-in-image/_index.md" >}}) or [Model in Image]({{< relref "/samples/domains/model-in-image/_index.md" >}}), then do not use the Administration Console to make changes to the WebLogic domain configuration as these changes are ephemeral and will be lost when servers restart. See [Choose a domain home source type]({{< relref "/managing-domains/choosing-a-model/_index.md" >}}).
+ * Do not use the WebLogic Server Administration Console to start or stop servers, or for scaling clusters. See [Starting and stopping servers]({{< relref "/managing-domains/domain-lifecycle/startup#starting-and-stopping-servers" >}}) and [Scaling]({{< relref "/managing-domains/domain-lifecycle/scaling.md" >}}).
+ * If your domain home type is either [Domain in Image]({{< relref "/samples/domains/domain-home-in-image/_index.md" >}}) or [Model in Image]({{< relref "/samples/domains/model-in-image/_index.md" >}}), then do not use the Administration Console to make changes to the WebLogic domain configuration because these changes are ephemeral and will be lost when servers restart. See [Choose a domain home source type]({{< relref "/managing-domains/choosing-a-model/_index.md" >}}).
 
 {{% notice warning %}}
 Externally exposing administrative, RMI, or T3 capable WebLogic channels
@@ -32,17 +32,17 @@ port forwarding, or a similar method can create an insecure configuration.
 For more information, see [External network access security]({{<relref "/security/domain-security/weblogic-channels.md">}}).
 {{% /notice %}}
 
-### Use a load balancer 
-To access WebLogic Server Administration Console through a load balancer, first set up an [Ingress]({{< relref "/managing-domains/accessing-the-domain/ingress/_index.md">}}). This, in combination with SSL, is the best practice approach for production use cases.
+### Use a load balancer
+To access the WebLogic Server Administration Console through a load balancer, first set up an [Ingress]({{< relref "/managing-domains/accessing-the-domain/ingress/_index.md">}}). This, in combination with SSL, is the best practice approach for production use cases.
 
-{{% notice note %}} The following `path-routing` ingress instructions do not apply when you need to concurrently access multiple domains in the same Kubernetes cluster through the same external load balancer port. For the multiple domain use case, see the [Host-based routing](https://github.com/oracle/weblogic-kubernetes-operator/blob/main/kubernetes/samples/charts/traefik/README.md#host-based-routing) sample and make sure that the host names are resolvable by your DNS server (e.g. `domain1.org` and `domain2.org` in the sample).
+{{% notice note %}} The following `path-routing` ingress instructions do not apply when you need to concurrently access multiple domains in the same Kubernetes cluster through the same external load balancer port. For the multiple domain use case, see the [Host-based routing](https://github.com/oracle/weblogic-kubernetes-operator/blob/main/kubernetes/samples/charts/traefik/README.md#host-based-routing) sample and make sure that the host names are resolvable by your DNS server (for example, `domain1.org` and `domain2.org` in the sample).
 {{% /notice %}}
 
 #### Configure ingress path routing rules for a non-SSL port
-The following example sets up an ingress path routing rule to access a WebLogic Server Administration Console through a non-SSL port. 
+The following example sets up an ingress path routing rule to access a WebLogic Server Administration Console through a non-SSL port.
 
 1. Set up a `path-routing` YAML file for a Traefik load balancer:
- 
+
    ```yaml
    apiVersion: traefik.containo.us/v1alpha1
    kind: IngressRoute
@@ -62,30 +62,30 @@ The following example sets up an ingress path routing rule to access a WebLogic
          port: 7001
    ```
 
-2. Open the following URL from your browser to access the WebLogic Server Administration Console:
+2. To access the WebLogic Server Administration Console, open the following URL from your browser:
 
    ```
    http://${HOSTNAME}:${LB_PORT}/console
    ```
    Where:
-   
+
      * `${HOSTNAME}` is where the ingress load balancer is running.
-   
+
      * To determine the `${LB_PORT}` when using a Traefik load balancer:
 
         `$ export LB_PORT=$(kubectl -n traefik get service traefik-operator -o jsonpath='{.spec.ports[?(@.name=="web")].nodePort}')`
 
-If you have an [FMW Infrastructure]({{< relref "/managing-fmw-domains.md" >}}) type domain, then you can add an ingress path routing rule for PathPrefix `/em` and access the Fusion Middleware Control (Enterprise Manager) Console using the following URL:
+If you have an [FMW Infrastructure]({{< relref "/managing-fmw-domains.md" >}}) domain, then you can add an ingress path routing rule for the PathPrefix `/em` and access Fusion Middleware Control (Enterprise Manager) using the following URL:
 
 ```
 http://${HOSTNAME}:${LB_PORT}/em
 ```
-#### Configure ingress path routing rules for a SSL port and enable `WebLogic Plugin Enabled`
-The following example sets up load balancer routing for access to a WebLogic Server Administration Console through a SSL port.
+#### Configure ingress path routing rules for an SSL port and enable `WebLogic Plugin Enabled`
+The following example sets up load balancer routing for access to the WebLogic Server Administration Console through an SSL port.
 
-1. Enable `WebLogic Plugin Enabled` setting in the WebLogic configuration: 
+1. Enable the `WebLogic Plugin Enabled` setting in the WebLogic configuration:
 
-   The WebLogic configuration setting `WebLogic plugin Enabled`, when set to true, informs the WebLogic Server about the presence of a load balancer proxy. Failure to have this setting enabled causes unexpected results in cases where the client IP address is required or when SSL terminates at the load balancer. 
+   The WebLogic configuration setting `WebLogic Plugin Enabled`, when set to `true`, informs WebLogic Server about the presence of a load balancer proxy. Failure to have this setting enabled causes unexpected results in cases where the client IP address is required or when SSL terminates at the load balancer.
 
    When using WDT to configure a WebLogic domain, use the resource section at the domain level in a model YAML file:
    ```yaml
@@ -104,7 +104,7 @@ The following example sets up load balancer routing for access to a WebLogic Ser
    ```
 2. Configure an ingress path routing rule and update the ingress resource with a `customRequestHeaders` value:
 
-   For example, see the following `path-routing` YAML file for a Traefik load balancer. In the case of SSL termination, Traefik must pass a custom header `WL-Proxy-SSL:true` to the WebLogic Server endpoints. 
+   For example, see the following `path-routing` YAML file for a Traefik load balancer. In the case of SSL termination, Traefik must pass a custom header `WL-Proxy-SSL:true` to the WebLogic Server endpoints.
 
    ```yaml
    apiVersion: traefik.containo.us/v1alpha1
@@ -115,7 +115,7 @@ The following example sets up load balancer routing for access to a WebLogic Ser
      name: traefik-console-tls
      namespace: weblogic-domain
    spec:
-     entryPoints: 
+     entryPoints:
       - websecure
      routes:
      - kind: Rule
@@ -142,17 +142,17 @@ The following example sets up load balancer routing for access to a WebLogic Ser
    ```
 3. Access the WebLogic Server Administration Console using the HTTPS port:
 
-   Get the SSL port from the Kubernetes service. 
+   Get the SSL port from the Kubernetes service:
    ```shell
    # Get the ingress controller secure web port
    $ SSLPORT=$(kubectl -n traefik get service traefik-operator -o jsonpath='{.spec.ports[?(@.name=="websecure")].nodePort}')
    ```
-   Use the following URL from your browser to access the WebLogic Server Administration Console:
+   From your browser, use the following URL to access the WebLogic Server Administration Console:
    ```
    https://${HOSTNAME}:${SSLPORT}/console
    ```
 
-   If you have an [FMW Infrastructure]({{< relref "/managing-fmw-domains.md" >}}) type domain, then you can add an ingress path routing rule for PathPrefix `/em` and access the Fusion Middleware Control (Enterprise Manager) Console using the following URL:
+   If you have an [FMW Infrastructure]({{< relref "/managing-fmw-domains.md" >}}) domain, then you can add an ingress path routing rule for the PathPrefix `/em` and access Fusion Middleware Control (Enterprise Manager) using the following URL:
 
    ```
    https://${HOSTNAME}:${SSLPORT}/em
@@ -162,25 +162,25 @@ The following example sets up load balancer routing for access to a WebLogic Ser
 
 Use the following steps to configure a `NodePort` to access the WebLogic Server Administration Console:
 
-1. Update the WebLogic Server configuration for the Administration Server to add a Network Access Point (custom channel) with the HTTP protocol, and expose this channel on a NodePort service using the `domain.spec.adminServer.adminService.channels` attribute.
+1. Update the WebLogic Administration Server configuration to add a Network Access Point (custom channel) with the HTTP protocol, and expose this channel on a NodePort service using the `domain.spec.adminServer.adminService.channels` attribute.
 
    For an example of setting up the `NodePort` on an Administration Server, see [Use a `NodePort`]({{< relref "/managing-domains/accessing-the-domain/wlst#use-a-nodeport" >}}). For information about the `NodePort` Service on an Administration Server, see the [Domain resource](https://github.com/oracle/weblogic-kubernetes-operator/blob/{{< latestMinorVersion >}}/documentation/domains/Domain.md) document.
 
-2. Use the following URL from your browser to access the WebLogic Server Administration Console:
+2. From your browser, use the following URL to access the WebLogic Server Administration Console:
 
    ```
    http://hostname:adminserver-NodePort/console
    ```
    The `adminserver-NodePort` is the port number of the Administration Server outside the Kubernetes cluster.
 
-   If you have an [FMW Infrastructure]({{< relref "/managing-fmw-domains.md" >}}) type domain, then you can also access the Fusion Middleware Control (Enterprise Manager) Console using the following URL:
-   
+   If you have an [FMW Infrastructure]({{< relref "/managing-fmw-domains.md" >}}) domain, then you can also access Fusion Middleware Control (Enterprise Manager) using the following URL:
+
    ```
    http://hostname:adminserver-NodePort/em
    ```
 
 ### Use a `kubectl port-forward` connection
-A Kubernetes port forward command is convenient for development use cases and is not recommended for production use cases. It creates a local process external to a Kubernetes cluster that accepts external traffic on a dedicated local port and forwards this traffic to a specific pod and port in the Kubernetes cluster. If you have multiple domains, then each domain will require its own dedicated port forward command and a separate local port.
+A Kubernetes port forward command is convenient for development use cases but is _not recommended_ for production use cases. It creates a local process external to a Kubernetes cluster that accepts external traffic on a dedicated local port and forwards this traffic to a specific pod and port in the Kubernetes cluster. If you have multiple domains, then each domain will require its own dedicated port forward command and a separate local port.
 
 1. Forward a local port (that is external to
    Kubernetes) to the administration port of the
@@ -189,10 +189,10 @@ A Kubernetes port forward command is convenient for development use cases and is
 
    **NOTE:** If you plan to access the WebLogic Server Administration Console from a browser
    on a different machine than the port forwarding command,
-   then the port forwarding command needs to specify a `--address` parameter
+   then the port forwarding command needs to specify an `--address` parameter
    with an externally accessible IP address for the machine that is running the command.
 
-1. Use the following URL in the browser:
+1. In the browser, use the following URL:
 
    ```
    http://${HOSTNAME}:${LOCAL_PORT}/console
@@ -201,12 +201,12 @@ A Kubernetes port forward command is convenient for development use cases and is
 
      * `${HOSTNAME}` is the DNS address or the IP address of the machine
        where the `kubectl port-forward` command is running. This is
-       customizable on the `port-forward` command using `--address` parameter 
+       customizable using the `--address` parameter
        and is `localhost` or `127.0.0.1`, by default.
 
      * `${LOCAL_PORT}` is the local port specified on the `kubectl port-forward` command line.
 
-   If you have an [FMW Infrastructure]({{< relref "/managing-fmw-domains.md" >}}) type domain, then you can also access the Fusion Middleware Control (Enterprise Manager) Console using the following URL:
+   If you have an [FMW Infrastructure]({{< relref "/managing-fmw-domains.md" >}}) domain, then you can also access Fusion Middleware Control (Enterprise Manager) using the following URL:
 
    ```
    http://${HOSTNAME}:${LOCAL_PORT}/em
@@ -226,4 +226,4 @@ $ curl http://${HOSTNAME}:${LB_PORT}/console > /dev/null && echo "Connection suc
 Connection succeeded.
 ```
 
-If successful, then you should see the "Connection succeeded" message in the output from the above command.
+If successful, then you will see the `Connection succeeded` message in the output from the command.