update doc for K8s resource names (#1641)

* update doc for K8s resource names

* fix typo

Author: rosemarymarano

docs-source/content/_index.md

@@ -2,7 +2,7 @@
 
 Oracle is finding ways for organizations using WebLogic Server to run important workloads, to move those workloads into the cloud. By certifying on industry standards, such as Docker and Kubernetes, WebLogic now runs in a cloud neutral infrastructure. In addition, we've provided an open source Oracle WebLogic Server Kubernetes Operator (the “operator”) which has several key features to assist you with deploying and managing WebLogic domains in a Kubernetes environment. You can:
 
-* Create WebLogic domains in a Kubernetes persistent volume. This persistent volume can reside in an NFS file system or other Kubernetes volume types.
+* Create WebLogic domains in a Kubernetes PersistentVolume. This PersistentVolume can reside in an NFS file system or other Kubernetes volume types.
 * Create a WebLogic domain in a Docker image.
 * Override certain aspects of the WebLogic domain configuration.
 * Define WebLogic domains as a Kubernetes resource (using a Kubernetes custom resource definition).
@@ -34,7 +34,7 @@ This release candidate was published on May 8, 2020.  There may be additional re
 
 This release candidate introduces _non-backward compatible_ changes.  This release candidate cannot be run in the same
 cluster as another release of the operator.  You can upgrade from 2.5.0 to 3.0.0-rc1 without needing to restart or recreate
-any existing domains. However, please note that we do plan to support running the final 3.0.0
+any existing domains. However, please note that we _do_ plan to support running the final 3.0.0
 release in the same cluster with at least one 2.x release of the operator to allow for staged migration.
 
 The feature changes in 3.0.0-rc1 are:
@@ -45,15 +45,15 @@ The feature changes in 3.0.0-rc1 are:
   the same model and automated updating of the domain based on model changes.
   The operator automates management of the domain encryption keys to ensure
   that they are not changed during domain updates.
-  A [sample]({{% relref "/samples/simple/domains/model-in-image" %}}) is also provided that
+  We provide a [sample]({{% relref "/samples/simple/domains/model-in-image" %}}) that
   demonstrates the key use cases for this feature.
 * Support for running the operator on Kubernetes 1.16.
 * Deprecation and removal of support for running the operator on Kubernetes 1.13
   and earlier versions.
 * Deprecation and removal of support for Helm 2.x.  Helm 2.x uses the "tiller" pod
   which needs to run with elevated privileges (`cluster-admin` or very close to that)
   and which could be a vector for a privilege escalation attack.  Helm 3.x removes
-  tiller and does not create the same exposure.
+  Tiller and does not create the same exposure.
 
 ***
 

docs-source/content/developerguide/asynchronous-call-model.md

@@ -6,7 +6,7 @@ weight: 7
 ---
 
 
-Our expectation is that customers will task the operator with managing hundreds of WebLogic domains across dozens of Kubernetes namespaces.  Therefore, we have designed the operator with an efficient user-level threads pattern.  We've used that pattern to implement an asynchronous call model for Kubernetes API requests.  This call model has built-in support for timeouts, retries with exponential back-off, and lists that exceed the requested maximum size using the continuance functionality.
+Our expectation is that customers will task the operator with managing hundreds of WebLogic domains across dozens of Kubernetes Namespaces.  Therefore, we have designed the operator with an efficient user-level threads pattern.  We've used that pattern to implement an asynchronous call model for Kubernetes API requests.  This call model has built-in support for timeouts, retries with exponential back-off, and lists that exceed the requested maximum size using the continuance functionality.
 
 #### User-level thread pattern
 

docs-source/content/faq/boot-identity-not-valid.md

@@ -13,6 +13,6 @@ When you see these kinds of errors, it means that the user name and password pro
 have also indicated that the WebLogic domain directory's security configuration files have changed in an incompatible way between when the operator scanned
 the domain directory, which occurs during the "introspection" phase, and when the server instance attempted to start. There is now a separate validation for that condition described in the [Domain secret mismatch](../domain-secret-mismatch/) FAQ entry.
 
-Check that the user name and password credentials stored in the Kubernetes secret referenced by `weblogicCredentialsSecret` contain the expected values for an account with administrative privilege for the WebLogic domain.
+Check that the user name and password credentials stored in the Kubernetes Secret referenced by `weblogicCredentialsSecret` contain the expected values for an account with administrative privilege for the WebLogic domain.
 Then [stop all WebLogic Server instances](https://oracle.github.io/weblogic-kubernetes-operator/userguide/managing-domains/domain-lifecycle/startup/#starting-and-stopping-servers)
 in the domain before restarting so that the operator will repeat its introspection and generate the corrected `boot.properties` files.

docs-source/content/faq/configmaps.md

@@ -1,22 +1,22 @@
 ---
-title: "Providing access to a Config Map"
+title: "Providing access to a ConfigMap"
 date: 2020-01-07T15:02:28-05:00
 draft: false
 weight: 70
 ---
-> I need to provide an instance with access to a Config Map.
+> I need to provide an instance with access to a ConfigMap.
 
-Configuration files can be supplied to Kubernetes pods and jobs by a 
-[ConfigMap](https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/#create-a-configmap), 
+Configuration files can be supplied to Kubernetes Pods and Jobs by a
+[ConfigMap](https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/#create-a-configmap),
 which consists of a set of key-value pairs. Each entry may be accessed by one or more operator-managed nodes
 as a read-only text file. Access can be provided across the domain, within a single cluster, or for a single server.
-In each case, the access is configured within the `serverPod` element of the desired scope. 
+In each case, the access is configured within the `serverPod` element of the desired scope.
 
 For example, given
 a ConfigMap named `my-map` with entries `key-1` and `key-2`, you can provide access to both values as separate files
 in the same directory within the `cluster-1` cluster with the following
 in your [domain resource](https://github.com/oracle/weblogic-kubernetes-operator/blob/master/docs/domains/Domain.md):
- 
+
 
 ```
   clusters:
@@ -26,7 +26,7 @@ in your [domain resource](https://github.com/oracle/weblogic-kubernetes-operator
       - name: my-volume-1
         configMap:
           name: my-map
-          items: 
+          items:
           - key: key-1
             path: first
           - key: key-2
@@ -36,8 +36,7 @@ in your [domain resource](https://github.com/oracle/weblogic-kubernetes-operator
         mountPath: /weblogic-operator/my
 
 ```
-This provides access to two files, found at paths `/weblogic-operator/my/first` and `/weblogic-operator/my/second`. 
-Both a `volume` and a `volumeMount` entry are required, and must have the same name. The name of the `ConfigMap` is 
+This provides access to two files, found at paths `/weblogic-operator/my/first` and `/weblogic-operator/my/second`.
+Both a `volume` and a `volumeMount` entry are required, and must have the same name. The name of the `ConfigMap` is
 specified in the `name` field under the `configMap` entry. The `items` entry is an array,
 in which each entry maps a `ConfigMap` key to a file name under the directory specified as `mountPath` under a `volumeMount`.
-

docs-source/content/faq/domain-secret-mismatch.md

@@ -17,8 +17,8 @@ To understand the "incompatible domain security configuration" type of failure,
 domain directory contains a `security` subdirectory that contains a file called `SerializedSystemIni.dat`.  This file contains
 security data to bootstrap the WebLogic domain, including a domain-specific encryption key.
 
-During introspection, the operator generates a Kubernetes job that runs a pod in the domain's Kubernetes namespace and with the
-same Kubernetes service account that will be used later to run the Administration Server. This pod has access to the Kubernetes
+During introspection, the operator generates a Kubernetes Job that runs a pod in the domain's Kubernetes Namespace and with the
+same Kubernetes ServiceAccount that will be used later to run the Administration Server. This pod has access to the Kubernetes
 secret referenced by `weblogicCredentialsSecret` and encrypts these values with the domain-specific encryption key so that the
 secured value can be injected in to the `boot.properties` files when starting server instances.
 

docs-source/content/faq/external-clients.md

@@ -31,7 +31,7 @@ Here are the steps:
 
 ##### Kubernetes `NodePorts`
 
-The Kubernetes `NodePorts` approach for giving external WebLogic EJB or JMS clients access to a Kubernetes hosted WebLogic cluster involves configuring a network channel on the desired WebLogic cluster that accepts T3 protocol traffic, and exposing a Kubernetes `NodePort` that redirects external network traffic on the Kubernetes nodes to the network channel.
+The Kubernetes `NodePorts` approach for giving external WebLogic EJB or JMS clients access to a Kubernetes hosted WebLogic cluster involves configuring a network channel on the desired WebLogic cluster that accepts T3 protocol traffic, and exposing a Kubernetes `NodePort` that redirects external network traffic on the Kubernetes Nodes to the network channel.
 
 
 {{% notice note %}} The `NodePort` approach is available only when worker nodes are accessible by the clients, for example, when they have public IP addresses. If private worker nodes are used and access to them is possible only through a load balancer or bastion, then the `NodePort` approach is not a valid option to provide access to external clients.
@@ -128,7 +128,7 @@ In this example:
 
 - WebLogic binds the custom network channel to port `7999` and the default network channel to `8001`.
 
-- The operator will automatically create a Kubernetes service named `DOMAIN_UID-cluster-cluster-1` for both the custom and default channel.
+- The operator will automatically create a Kubernetes Service named `DOMAIN_UID-cluster-cluster-1` for both the custom and default channel.
 
 - Internal clients running in the same Kubernetes cluster as the channel can access the cluster using `t3://DOMAIN_UID-cluster-cluster-1:8001`.
 

docs-source/content/faq/namespace-management.md

@@ -5,7 +5,7 @@ draft: false
 weight: 1
 ---
 
-Each operator deployment manages a number of Kubernetes namespaces. For more information, see [Operator Helm configuration values]({{< relref "/userguide/managing-operators/using-the-operator/using-helm#operator-helm-configuration-values" >}}). A number of Kubernetes resources
+Each operator deployment manages a number of Kubernetes Namespaces. For more information, see [Operator Helm configuration values]({{< relref "/userguide/managing-operators/using-the-operator/using-helm#operator-helm-configuration-values" >}}). A number of Kubernetes resources
 must be present in a namespace before any WebLogic domain custom resources can be successfully
 deployed into it.
 Those Kubernetes resources are created either as part of the installation
@@ -16,7 +16,7 @@ This FAQ describes some considerations to be aware of when you manage the namesp
 * [Check the namespaces that the operator manages](#check-the-namespaces-that-the-operator-manages)
 * [Add a namespace for the operator to manage](#add-a-kubernetes-namespace-to-the-operator)
 * [Delete a namespace from the operator's domain namespace list](#delete-a-kubernetes-namespace-from-the-operator)
-* [Delete and recreate a Kubernetes namespace that the operator manages](#recreate-a-previously-deleted-kubernetes-namespace)
+* [Delete and recreate a Kubernetes Namespace that the operator manages](#recreate-a-previously-deleted-kubernetes-namespace)
 
 For others, see [Common Mistakes and Solutions]({{< relref "/userguide/managing-operators/using-the-operator/using-helm#common-mistakes-and-solutions" >}}).
 
@@ -58,7 +58,7 @@ $ helm list --namespace <namespace>
 $ helm list --all-namespaces
 ```
 
-#### Add a Kubernetes namespace to the operator
+#### Add a Kubernetes Namespace to the operator
 If you want an operator deployment to manage a namespace, you need to add the namespace to the operator's `domainNamespaces` list. Note that the namespace has to already exist, for example, using the `kubectl create` command.
 
 Adding a namespace to the `domainNamespaces` list tells the operator deployment or runtime
@@ -98,7 +98,7 @@ NAME                 DATA      AGE
 weblogic-domain-cm   14        12m
 ```
 
-####  Delete a Kubernetes namespace from the operator
+####  Delete a Kubernetes Namespace from the operator
 When you no longer want a namespace to be managed by the operator, you need to remove it from
 the operator's `domainNamespaces` list, so that the corresponding Kubernetes resources that are
 associated with the namespace can be cleaned up.
@@ -118,7 +118,7 @@ $ helm upgrade \
 
 ```
 
-#### Recreate a previously deleted Kubernetes namespace
+#### Recreate a previously deleted Kubernetes Namespace
 
 If you need to delete a namespace (and the resources in it) and then recreate it,
 remember to remove the namespace from the operator's `domainNamespaces` list

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

@@ -26,13 +26,13 @@ see [Persistent storage]({{< relref "/userguide/managing-domains/persistent-stor
 #### 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
+uses a Kubernetes Job to create the domain. The sample uses an
 `initContainers` section to change the file ownership which will
 fail for OCI FSS created volumes used with an OKE cluster.
 
 The OCI FSS volume contains some files that are not modifiable thus
-causing the Kubernetes job to fail. The failure is seen in the
-description of the Kubernetes job pod:
+causing the Kubernetes Job to fail. The failure is seen in the
+description of the Kubernetes Job pod:
 ```bash
 $ kubectl describe -n domain1-ns pod domain1-create-weblogic-sample-domain-job-wdkvs
    :

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

@@ -9,7 +9,7 @@ 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.
+ingress controller like Traefik or Voyager.
 
 OKE Kubernetes worker nodes typically do not have public IP addresses.
 This means that the `NodePort` services created by the operator are
@@ -20,8 +20,8 @@ to services running in OKE.
 
 {{% notice note %}}
 It is also possible, if desirable, to have an OCI load balancer route
-traffic to an Ingress controller running inside the Kubernetes cluster
-and have that Ingress controller in turn route traffic to services in the
+traffic to an ingress controller running inside the Kubernetes cluster
+and have that ingress controller in turn route traffic to services in the
 cluster.
 {{% /notice %}}
 

docs-source/content/faq/volumes.md

@@ -1,10 +1,10 @@
 ---
-title: "Providing access to a Persistent Volume Claim"
+title: "Providing access to a PersistentVolumeClaim"
 date: 2020-01-07T15:02:28-05:00
 draft: false
 weight: 60
 ---
-> I need to provide an instance with access to a Persistent Volume Claim.
+> I need to provide an instance with access to a PersistentVolumeClaim.
 
 Some applications need access to a file, either to read data or to provide additional logging beyond what is
 built into the operator. One common way of doing that within Kubernetes is to create a