Cherry-pick branch 'rm/link-FAQ-WLST' into 'release/4.1'

Author: rjeberhard

documentation/site/content/faq/resource-settings.md

@@ -115,7 +115,7 @@ In later versions of Kubernetes, it is possible to fine tune scheduling and evic
 ### Java heap size and memory resource considerations
 
 {{% notice note %}}
-Oracle recommends configuring Java heap sizes for WebLogic JVMs instead of relying on the defaults.
+Oracle recommends configuring Java heap sizes for WebLogic JVMs instead of relying on the defaults. For detailed information about memory settings when running WLST from the pod where the WLS server is running, see [Use `kubectl exec`]({{< relref "/managing-domains/accessing-the-domain/wlst#use-kubectl-exec" >}}).
 {{% /notice %}}
 
 #### Importance of setting heap size and memory resources
@@ -204,7 +204,7 @@ There's no memory or CPU limit configured by default in samples and so the defau
 If you wish to set resource requests or limits differently on a sample Domain or Cluster YAML file or template, see [Setting resource requests and limits in a Domain or Cluster resource](#setting-resource-requests-and-limits-in-a-domain-or-cluster-resource). Or, for samples that generate their Domain resource using an "inputs" YAML file, see the `serverPodMemoryRequest`, `serverPodMemoryLimit`, `serverPodCpuRequest`, and `serverPodCpuLimit` parameters in the sample's `create-domain.sh` inputs file.
 
 #### Burstable pods and JDK active processor count calculation
-If you have [Burstable Pods](https://kubernetes.io/docs/tasks/configure-pod-container/quality-service-pod/#create-a-pod-that-gets-assigned-a-qos-class-of-burstable) that configure the CPU resource requests but have no CPU limits, then the JDK can incorrectly calculate the active processor count. The JDK interprets the value of the `--cpu-shares` parameter (which maps to `spec.containers[].resources.requests.cpu`) to limit how many CPUs the current process can use, as explained in [JDK-8288367](https://bugs.openjdk.org/browse/JDK-8288367). This might cause the JVM to use fewer CPUs than available, leading to an under utilization of CPU resources when running in a Kubernetes environment. Updating the JDK to newer versions, `JDK 8u371` or `JDK 11.0.17`, fixes this. 
+If you have [Burstable Pods](https://kubernetes.io/docs/tasks/configure-pod-container/quality-service-pod/#create-a-pod-that-gets-assigned-a-qos-class-of-burstable) that configure the CPU resource requests but have no CPU limits, then the JDK can incorrectly calculate the active processor count. The JDK interprets the value of the `--cpu-shares` parameter (which maps to `spec.containers[].resources.requests.cpu`) to limit how many CPUs the current process can use, as explained in [JDK-8288367](https://bugs.openjdk.org/browse/JDK-8288367). This might cause the JVM to use fewer CPUs than available, leading to an under utilization of CPU resources when running in a Kubernetes environment. Updating the JDK to newer versions, `JDK 8u371` or `JDK 11.0.17`, fixes this.
 
 {{% notice note %}}
 To override the number of CPUs that the JVM automatically detects and uses when creating threads for various subsystems, use the `-XX:ActiveProcessorCount` Java option.

documentation/site/content/managing-domains/accessing-the-domain/wlst.md

@@ -25,20 +25,20 @@ You can use the `kubectl exec` command to start an interactive WLST session
 within a pod or to remotely run a WLST script on a pod.
 Typically, this is the preferred method.
 
-**NOTE**: The WLST script uses the value of the environment variable `USER_MEM_ARGS` to control the heap settings of the JVM process.  If you have set the environment variable 
+**NOTE**: The WLST script uses the value of the environment variable `USER_MEM_ARGS` to control the heap settings of the JVM process.  If you have set the environment variable
 `USER_MEM_ARGS` in the domain resource YAML, the WLST process will inherit the memory settings.  For example,
 if you have `USER_MEM_ARGS` value set to `-Xms2048m -Xmx2048m`, the WebLogic server JAVA process will use this heap settings, and if you run the WLST script in the server pod,
 the WLST script JAVA process will also use this heap settings. This may cause unexpected behavior in the server pod due to additional memory usage.  
 
-In order to change the memory settings, you must do the following 
+In order to change the memory settings, you must do the following:
 
 
 ```shell
 USER_MEM_ARGS="" $ORACLE_HOME/oracle_common/common/bin/wlst.sh
 ```
-This will unset the `USER_MEM_ARGS` and let the WLST to use the default heap size `-Xms32m -Xmx1024m`, and this only affect the WLST script process.  
+This will unset the `USER_MEM_ARGS` and let WLST use the default heap size, `-Xms32m -Xmx1024m`; this only affects the WLST script process.  
 
-If you want to use different memory settings, you can adjust it by 
+If you want to use different memory settings, you can adjust it by
 
 ```shell
 USER_MEM_ARGS="-Xms128m -Xmx128m" $ORACLE_HOME/oracle_common/common/bin/wlst.sh