summaryrefslogtreecommitdiffstats
path: root/docs/platform/installation
diff options
context:
space:
mode:
authoranjali.walsatwar <anjali.walsatwar@huawei.com>2019-08-02 11:43:15 +0530
committeranjali.walsatwar <anjali.walsatwar@huawei.com>2019-08-02 11:43:15 +0530
commitfa092c52d71f9bcb0dbc51aadcfe8551beb5b8be (patch)
tree0911231342594f117a54bd0058974f7a3b8dbf29 /docs/platform/installation
parent8efaf0a28dc2b26be9871ccfd1a376e34b372bb6 (diff)
documents have different spelling mistakes and grammatical issues
fix for documents mistakes Issue-ID: USECASEUI-291 Signed-off-by: anjali.walsatwar <anjali.walsatwar@huawei.com> Change-Id: I546c3196c211e5607fd6b20ac112a76783cb0904
Diffstat (limited to 'docs/platform/installation')
-rw-r--r--docs/platform/installation/installation/uui-over-oom.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/platform/installation/installation/uui-over-oom.rst b/docs/platform/installation/installation/uui-over-oom.rst
index dcf6bce5..88235d94 100644
--- a/docs/platform/installation/installation/uui-over-oom.rst
+++ b/docs/platform/installation/installation/uui-over-oom.rst
@@ -42,20 +42,20 @@ https://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_quickstart_gui
1. First ensure Usecase-UI is marked true against field enabled in the oom/kubernetes/onap/values.yaml for successful deployment.
2. Upgrade Images in OOM charts to ensure the component version is right, you should check the respective component image version in Usecase-UI charts.
-If you need update the version, please modify values.yaml files.
+If you need to update the version, please modify values.yaml files.
3. Rebuild all repos in helm. Every time you change the charts, you need to rebuild all repos to ensure the change can take effect.
**4. Debug and Testing in running Pod**
=======================================
-When you are doing the testing and would like to replace some new file like binary or some script and want to check the new resut.
+When you are doing the testing and would like to replace some new file like binary or some script and want to check the new result.
Before you replace the file to the running pod,you need to close the pod livenessProbe and readinessProbe first to avoid the pod restart.
**5. Kubectl basic command**
============================
-Basic operation of kubernests cluster(Take the namespace of onap in linux client as an example)
+Basic operation of kubernetes cluster(Take the namespace of onap in linux client as an example)
* Check the cluster node