From b90e8fce4527322fdd35840b1ee8eab0d7ad4ca4 Mon Sep 17 00:00:00 2001 From: "guillaume.lambert" Date: Sun, 26 Sep 2021 21:28:50 +0200 Subject: [PATCH] [DOC] Fix a few mispellings Many words were advertised by the spell checker. Some of them are obviously mispelled and are fixed here. Issue-ID: DOC-710 Signed-off-by: guillaume.lambert Change-Id: I4108ba7e5d89099d16ae5714609a9701137ae83c --- docs/oom_setup_ingress_controller.rst | 4 ++-- docs/oom_setup_kubernetes_rancher.rst | 2 +- docs/oom_setup_paas.rst | 2 +- docs/oom_user_guide.rst | 8 ++++---- docs/release-notes-beijing.rst | 10 +++++----- docs/release-notes-casablanca.rst | 2 +- docs/release-notes-dublin.rst | 2 +- docs/release-notes-elalto.rst | 2 +- docs/release-notes-honolulu.rst | 2 +- 9 files changed, 17 insertions(+), 17 deletions(-) diff --git a/docs/oom_setup_ingress_controller.rst b/docs/oom_setup_ingress_controller.rst index e49c72a2e4..cb385da141 100644 --- a/docs/oom_setup_ingress_controller.rst +++ b/docs/oom_setup_ingress_controller.rst @@ -139,8 +139,8 @@ MetalLB Load balancer can be easily installed using automatic install script:: > ./install-metallb-on-cluster.sh -Configuration Ngninx ingress controller -======================================= +Configuration Nginx ingress controller +====================================== After installation DNS server and ingress controller we can install and configure ingress controller. diff --git a/docs/oom_setup_kubernetes_rancher.rst b/docs/oom_setup_kubernetes_rancher.rst index e002d38897..6272f83238 100644 --- a/docs/oom_setup_kubernetes_rancher.rst +++ b/docs/oom_setup_kubernetes_rancher.rst @@ -428,7 +428,7 @@ share a common, distributed filesystem. In this tutorial, we will setup an NFS Master, and configure all Worker nodes a Kubernetes cluster to play the role of NFS slaves. -It is recommneded that a separate VM, outside of the kubernetes +It is recommended that a separate VM, outside of the kubernetes cluster, be used. This is to ensure that the NFS Master does not compete for resources with Kubernetes Control Plane or Worker Nodes. diff --git a/docs/oom_setup_paas.rst b/docs/oom_setup_paas.rst index 845fd473e0..6b7b9c3bab 100644 --- a/docs/oom_setup_paas.rst +++ b/docs/oom_setup_paas.rst @@ -16,7 +16,7 @@ Starting from Honolulu release, Cert-Manager and Prometheus Stack are a part of k8s PaaS for ONAP operations and can be installed to provide additional functionality for ONAP engineers. -The versions of PaaS compoents that are supported by OOM are as follows: +The versions of PaaS components that are supported by OOM are as follows: .. table:: ONAP PaaS components diff --git a/docs/oom_user_guide.rst b/docs/oom_user_guide.rst index 5f63c7d1a2..3212fd319d 100644 --- a/docs/oom_user_guide.rst +++ b/docs/oom_user_guide.rst @@ -570,7 +570,7 @@ Below is the example for the same:: Here the Name column shows the RELEASE NAME, In our case we want to try the scale operation on cassandra, thus the RELEASE NAME would be dev-cassandra. -Now we need to obtain the chart name for casssandra. Use the below +Now we need to obtain the chart name for cassandra. Use the below command to get the chart name:: > helm search cassandra @@ -585,15 +585,15 @@ Below is the example for the same:: local/sdc-cs 8.0.0 ONAP Service Design and Creation Cassandra Here the Name column shows the chart name. As we want to try the scale -operation for cassandra, thus the correponding chart name is local/cassandra +operation for cassandra, thus the corresponding chart name is local/cassandra Now we have both the command's arguments, thus we can perform the -scale opeartion for cassandra as follows:: +scale operation for cassandra as follows:: > helm upgrade dev-cassandra local/cassandra --set replicaCount=3 -Using this command we can scale up or scale down the cassadra db instances. +Using this command we can scale up or scale down the cassandra db instances. The ONAP components use Kubernetes provided facilities to build clustered, diff --git a/docs/release-notes-beijing.rst b/docs/release-notes-beijing.rst index 1172a086d2..84f86c100d 100644 --- a/docs/release-notes-beijing.rst +++ b/docs/release-notes-beijing.rst @@ -231,7 +231,7 @@ Bug * [`OOM-514 `_] - Readiness prob fails sometimes even though the relevant pods are running * [`OOM-539 `_] - Kube2MSB registrator doesn't support https REST service registration * [`OOM-570 `_] - Wrong value is assigned to kube2msb AUTH_TOKEN environment variable -* [`OOM-574 `_] - OOM configuration for robot doesnt copy heat templatese in dockerdata-nfs +* [`OOM-574 `_] - OOM configuration for robot does not copy heat templatese in dockerdata-nfs * [`OOM-577 `_] - Incorrect evaluation of bash command in yaml template file (portal-vnc-dep.yaml) * [`OOM-578 `_] - Hard coded token in oom/kubernetes/kube2msb/values.yaml file * [`OOM-589 `_] - Can not acces CLI in vnc-portal @@ -299,7 +299,7 @@ Bug * [`OOM-913 `_] - Consul agent pod is failing * [`OOM-916 `_] - Used to fix testing issues related to usability * [`OOM-918 `_] - Policy - incorrect configmap mount causes base.conf to disappear -* [`OOM-920 `_] - Issue with CLAMP configuation +* [`OOM-920 `_] - Issue with CLAMP configuration * [`OOM-921 `_] - align onap/values.yaml and onap/resources/environments/dev.yaml - different /dockerdata-nfs * [`OOM-926 `_] - Disable clustering for APP-C out-of-the-box * [`OOM-927 `_] - Need a production grade configuration override file of ONAP deployment @@ -316,7 +316,7 @@ Bug * [`OOM-948 `_] - make vfc got an error * [`OOM-951 `_] - Update APPC charts based on on changes for ccsdk and Nitrogen ODL * [`OOM-953 `_] - switch aai haproxy/hbase repo from hub.docker.com to nexus3 -* [`OOM-958 `_] - SDC-be deployment missing environment paramter +* [`OOM-958 `_] - SDC-be deployment missing environment parameter * [`OOM-964 `_] - SDC Healthcheck failure on sdc-be and sdc-kb containers down * [`OOM-968 `_] - warning on default deployment values.yaml * [`OOM-969 `_] - oomk8s images have no Dockerfile's @@ -330,7 +330,7 @@ Bug * [`OOM-993 `_] - AAI model-loader.properties not in sync with project file * [`OOM-994 `_] - DCAE cloudify controller docker image 1.1.0 N/A - use 1.2.0/1.3.0 * [`OOM-1003 `_] - dcae-cloudify-manager chart references obsolete image version -* [`OOM-1004 `_] - aai-resources constantly fails due to cassanda hostname +* [`OOM-1004 `_] - aai-resources constantly fails due to cassandra hostname * [`OOM-1005 `_] - AAI Widgets not loading due to duplicate volumes * [`OOM-1007 `_] - Update dcae robot health check config * [`OOM-1008 `_] - Set default consul server replica count to 1 @@ -366,7 +366,7 @@ Bug * [`OOM-1068 `_] - Update SO with new AAI cert * [`OOM-1076 `_] - some charts still using readiness check image from amsterdam 1.x * [`OOM-1077 `_] - AAI resources and traversal deployment failure on non-rancher envs -* [`OOM-1079 `_] - Robot charts dont allow over ride of pub_key, dcae_collector_ip and dcae_collector_port +* [`OOM-1079 `_] - Robot charts do not allow over ride of pub_key, dcae_collector_ip and dcae_collector_port * [`OOM-1081 `_] - Remove component 'mock' from TOSCA deployment * [`OOM-1082 `_] - Wrong pv location of dcae postgres * [`OOM-1085 `_] - appc hostname is incorrect in url diff --git a/docs/release-notes-casablanca.rst b/docs/release-notes-casablanca.rst index 6a6a196b6b..6b857309aa 100644 --- a/docs/release-notes-casablanca.rst +++ b/docs/release-notes-casablanca.rst @@ -30,7 +30,7 @@ areas: class provisioner * CPU and Memory limits in Helm Charts to improve Pod placement based on - resource availablity in Kubernetes Cluster + resource availability in Kubernetes Cluster * Support of Node Selectors for Pod placement diff --git a/docs/release-notes-dublin.rst b/docs/release-notes-dublin.rst index 1974756ea3..7a32297210 100644 --- a/docs/release-notes-dublin.rst +++ b/docs/release-notes-dublin.rst @@ -27,7 +27,7 @@ Summary **Platform Resiliency** -* Documenation of a Highly-Available Kubernetes Cluster Deployment +* Documentation of a Highly-Available Kubernetes Cluster Deployment * Availability of a Default Storage Class Provisioner for improved Persistent Storage resiliency * Availability of a CNI reference integration for Multi-site support diff --git a/docs/release-notes-elalto.rst b/docs/release-notes-elalto.rst index bbbf271a5f..b4059028e5 100644 --- a/docs/release-notes-elalto.rst +++ b/docs/release-notes-elalto.rst @@ -26,7 +26,7 @@ Version 5.0.1 (El Alto Release) Summary ------- -The focus of this release was on maintanence and as such no new features were +The focus of this release was on maintenance and as such no new features were delivered. A list of issues resolved in this release can be found here: https://jira.onap.org/projects/OOM/versions/10726 diff --git a/docs/release-notes-honolulu.rst b/docs/release-notes-honolulu.rst index 0c8d81f164..59f40ec0fa 100644 --- a/docs/release-notes-honolulu.rst +++ b/docs/release-notes-honolulu.rst @@ -136,7 +136,7 @@ Workarounds ----------- - ``_ - Workaround is to generate a password with "short" strenght or pregenerate + Workaround is to generate a password with "short" strength or pregenerate passwords without single quote in it. Default deployment is using "short" password generation for mariadb. -- 2.16.6