Rmarano (#1431)

* create image with Image Tool

* fix JDK version number

* FIX MISTAKES YIKES

* additional edits

* nit fixing

Author: rosemarymarano

docs-source/content/faq/oci-fss-pv.md

@@ -5,7 +5,7 @@ draft: false
 weight: 6
 ---
 
-If you are running your Kubernetes cluster on Oracle Container Engine 
+If you are running your Kubernetes cluster on Oracle Container Engine
 for Kubernetes (commonly known as OKE), and you use OCI File Storage (FSS)
 for persistent volumes to store the WebLogic domain home, then the file system
 handling demonstrated in the operator persistent volume sample will require
@@ -23,7 +23,7 @@ see [Persistent storage]({{< relref "/userguide/managing-domains/persistent-stor
 {{% /notice %}}
 
 
-### Failure during domain creation with persistent volume sample
+#### Failure during domain creation with persistent volume sample
 
 The existing sample for [creation of a domain home on persistent volume](https://github.com/oracle/weblogic-kubernetes-operator/tree/master/kubernetes/samples/scripts/create-weblogic-domain/domain-home-on-pv)
 uses a Kubernetes job to create the domain. The sample uses an
@@ -60,7 +60,7 @@ Init Containers:
    :
 ```
 
-### Updating the domain on persistent volume sample
+#### Updating the domain on persistent volume sample
 In the following snippet of the [create-domain-job-template.yaml](https://github.com/oracle/weblogic-kubernetes-operator/blob/master/kubernetes/samples/scripts/create-weblogic-domain/domain-home-on-pv/create-domain-job-template.yaml),
 you can see the updated `command` for the init container:
 ```

docs-source/content/faq/oci-lb.md

@@ -4,14 +4,14 @@ date: 2019-09-25T12:41:38-04:00
 draft: false
 ---
 
-If you are running your Kubernetes cluster on Oracle Container Engine 
+If you are running your Kubernetes cluster on Oracle Container Engine
 for Kubernetes (commonly known as OKE), you can have OCI automatically
 provision load balancers for you by creating a `Service` of type
 `LoadBalancer` instead of (or in addition to) installing an
 ingress controller like Traefik or Voyager.
 
 OKE Kubernetes worker nodes normally do not have public IP addresses.
-This means that the `NodePort` services created by the operator are 
+This means that the `NodePort` services created by the operator are
 not usable, because they would expose ports on the worker node's private
 IP addresses only, which are not reachable from outside the cluster.  
 Instead, you can use an OCI Load Balancer to provide access
@@ -25,23 +25,23 @@ cluster.
 {{% /notice %}}
 
 
-### Requesting an OCI Load Balancer
+#### Requesting an OCI Load Balancer
 
-When your domain is created by the operator, a number of Kubernetes 
-services are created by the operator, including one for the WebLogic 
+When your domain is created by the operator, a number of Kubernetes
+services are created by the operator, including one for the WebLogic
 Administration Server and one for each managed server and cluster.
 
 In the example below, there is a domain called `bobs-bookstore` in the
-`bob` namespace.  This domain has a cluster called `cluster-1` which 
+`bob` namespace.  This domain has a cluster called `cluster-1` which
 exposes traffic on port `31111`.
 
 The Kubernetes YAML file below defines a new `Service` in the same
 namespace.  The `selector` targets all of the pods in this namespace
-which are part of the cluster `cluster-1`, using the annotations that 
-are placed on those pods by the operator.  It also defines the port and 
+which are part of the cluster `cluster-1`, using the annotations that
+are placed on those pods by the operator.  It also defines the port and
 protocol.
 
-You can include the optional `oci-load-balancer-shape` annotation (as 
+You can include the optional `oci-load-balancer-shape` annotation (as
 shown) if you want to specify the shape of the load balancer.  Otherwise
 the default shape (100Mbps) will be used.
 
@@ -95,7 +95,6 @@ bobs-bookstore-oci-lb-service          LoadBalancer   10.96.121.216   132.145.23
 ```
 
 You can now use the external IP address and port to access your pods.  There are several
-options that can be used to configure more advanced load balancing behavior.  Please 
+options that can be used to configure more advanced load balancing behavior.  Please
 refer to the [OCI documentation](https://docs.cloud.oracle.com/iaas/Content/ContEng/Tasks/contengcreatingloadbalancer.htm)
 for more information, including how to configure SSL support, supporting internal and external subnets, and so on.
-

docs-source/content/samples/simple/domains/soa-domain/_index.md

@@ -7,7 +7,7 @@ PVC, and the domain resource YAML file for deploying the generated SOA domain."
 ---
 
 {{% notice warning %}}
-Oracle SOA Suite is currently only supported for non-production use in Docker and Kubernetes.  The information provided
+Oracle SOA Suite is currently supported only for non-production use in Docker and Kubernetes.  The information provided
 in this document is a *preview* for early adopters who wish to experiment with Oracle SOA Suite in Kubernetes before
 it is supported for production use.
 {{% /notice %}}
@@ -22,15 +22,15 @@ artifacts of the corresponding domain.
 Before you begin, we recommend the following:
 
 * Review the [Domain resource]({{< relref "/userguide/managing-domains/domain-resource/_index.md" >}}) documentation.
-* Review the [operator-prerequisites](https://oracle.github.io/weblogic-kubernetes-operator/userguide/introduction/introduction/#operator-prerequisites) 
+* Review the [operator-prerequisites](https://oracle.github.io/weblogic-kubernetes-operator/userguide/introduction/introduction/#operator-prerequisites)
 section for the supported versions of Kubernetes and Helm.
 * Complete the preliminary required steps documented [here]({{< relref "/userguide/managing-fmw-domains/soa-suite/_index.md" >}}).
 
 
 #### Prepare to use the create domain script
 
 The sample scripts for Oracle SOA Suite domain deployment are available at `<weblogic-kubernetes-operator-project>/kubernetes/samples/scripts/create-soa-domain`.
-  
+
 You must edit `create-domain-inputs.yaml` (or a copy of it) to provide the details for your domain.
 Please refer to the configuration parameters below to understand what information you must
 provide in this file.
@@ -160,45 +160,45 @@ metadata:
 spec:
   # The WebLogic Domain Home
   domainHome: /u01/oracle/user_projects/domains/soainfra
- 
+
   # If the domain home is in the image
   domainHomeInImage: false
- 
+
   # The WebLogic Server Docker image that the Operator uses to start the domain
   image: "container-registry.oracle.com/middleware/soasuite:12.2.1.3"
- 
+
   # imagePullPolicy defaults to "Always" if image version is :latest
   imagePullPolicy: "IfNotPresent"
- 
+
   # Identify which Secret contains the credentials for pulling an image
   #imagePullSecrets:
   #- name:
- 
+
   # Identify which Secret contains the WebLogic Admin credentials (note that there is an example of
   # how to create that Secret at the end of this file)
   webLogicCredentialsSecret:
     name: soainfra-domain-credentials
- 
+
   # Whether to include the server out file into the pod's stdout, default is true
   includeServerOutInPodLog: true
- 
+
   # Whether to enable log home
   logHomeEnabled: true
- 
+
   # The in-pod location for domain log, server logs, server out, and Node Manager log files
   logHome: /u01/oracle/user_projects/domains/logs/soainfra
   # An (optional) in-pod location for data storage of default and custom file stores.
   # If not specified or the value is either not set or empty (e.g. dataHome: "") then the
   # data storage directories are determined from the WebLogic domain home configuration.
   dataHome: ""
- 
+
   # serverStartPolicy legal values are "NEVER", "IF_NEEDED", or "ADMIN_ONLY"
   # This determines which WebLogic Servers the Operator will start up when it discovers this Domain
   # - "NEVER" will not start any server in the domain
   # - "ADMIN_ONLY" will start up only the administration server (no managed servers will be started)
   # - "IF_NEEDED" will start all non-clustered servers, including the administration server and clustered servers up to the replica count
   serverStartPolicy: "IF_NEEDED"
- 
+
   serverService:
     precreateService: true
 
@@ -216,7 +216,7 @@ spec:
     volumeMounts:
     - mountPath: /u01/oracle/user_projects
       name: weblogic-domain-storage-volume
- 
+
   # adminServer is used to configure the desired behavior for starting the administration server.
   adminServer:
     # serverStartState legal values are "RUNNING" or "ADMIN"
@@ -230,7 +230,7 @@ spec:
     #      nodePort: 30701
     # Uncomment to export the T3Channel as a service
     #    - channelName: T3Channel
- 
+
   # clusters is used to configure the desired behavior for starting member servers of a cluster.
   # If you use this entry, then the rules will be applied to ALL servers that are members of the named clusters.
   clusters:
@@ -241,7 +241,7 @@ spec:
     replicas: 2
   # The number of managed servers to start for unlisted clusters
   # replicas: 1
- 
+
   - clusterName: soa_cluster
     serverService:
       precreateService: true
@@ -463,7 +463,7 @@ $ kubectl get services -n NAMESPACE
 ```
 
 Here is an example of the output of this command. You can verify that services for Administration Server and Managed Servers (for SOA and OSB clusters) are created for `soaessosb` domain type.
-  
+
 ```
 $ kubectl get services -n soans
 NAME                            TYPE           CLUSTER-IP       EXTERNAL-IP   PORT(S)                       AGE

docs-source/content/userguide/managing-fmw-domains/soa-suite/_index.md

@@ -329,4 +329,3 @@ type: Opaque
 
 Now that you have your Docker images and you have created your RCU schemas, you are ready
 to create your domain.  To continue, follow the instructions in the [SOA Domain sample]({{< relref "/samples/simple/domains/soa-domain/_index.md" >}}).
-