Add copy to private repo docu (#1101)

Signed-off-by: Andy Tael <andy.tael@yahoo.com>

Author: andytael

docs-source/site/docs/setup/obtaining.md

@@ -8,6 +8,7 @@ The installation package is in the [helm](http://tbd) directory which  contains
 
 ```text
 .
+├── private_repo_helper.sh
 ├── obaas
 ├── obaas-db
 ├── obaas-observability

docs-source/site/docs/setup/prereqs.md

@@ -7,8 +7,8 @@ sidebar_position: 2
 To install OBaaS 2.0.0-M3, you must meet the following prerequisites:
 
 - A CNCF-compliant Kubernetes cluster with working storage provider that provides a storage class for RWX PVs, and ingress. Version 1.33.1. At least 3 worker nodes. At least 2 OCPU and 32GB memory per worker node (this allows for ONE installation of OBaaS and some applications.  As a general rule of thumb, double the number of worker nodes if you want to install TWO OBaaS instances. You may need more if you want to install additional applications). OKE "quick create/enhanced" cluster recommended.
-
 - An Oracle Database. Must be version 19c or later. If you want to use the AI features, it must be 23ai. Oracle Autonomous Database 23ai ATP with 2 ECPU and 1TB storage with "secure access from anywhere recommended.
+- If you plan to use a private image repository, the images must be copied there. OBaaS provides a helper script, `private_repo_helper.sh`, to perform this task.
 
 **Important note:** If your environment does not meet the prerequisites, the installation will fail. Please do not continue with installation until you have confirmed your environment meets the requirements.
 

docs-source/site/docs/setup/setup.md

@@ -27,7 +27,7 @@ Please note the following known issues in M3:
 
 The next release, 2.0.0-M4 is intended to be available approximately two weeks after M3 and to address some, if not all, of these limitations.
 
-**Important note:** Make sure that you have the correct kubectl config set. You can do this by exporting the KUBECONFIG variable and pointing to the correct config file.
+**Important note:** Make sure that you have the correct kubectl config set. You can do this by exporting the `KUBECONFIG` variable and pointing to the correct config file.
 
 ### High Level Installation Flow