Master idm 22.4.1 release (#136)

Author: manjunathdhegde-2910

docs-source/content/oam/patch-and-upgrade/upgrade-elk.md

@@ -17,7 +17,7 @@ If you are upgrading from July 22 (22.3.1) or earlier, to October 22 (22.4.1) or
 
 1. Make sure you have downloaded the latest code repository as per [Download the latest code repository](../upgrade-an-ingress/#download-the-latest-code-repository)
 
-1. If your domain namespace is anything other than `oamns`, edit the `$WORKDIR/kubernetes/elasticsearch-and-kibana/elasticsearch_and_kibana.yaml` and change all instances of `namespace: "oamns"` to your domain namespace.
+1. Edit the `$WORKDIR/kubernetes/elasticsearch-and-kibana/elasticsearch_and_kibana.yaml` and change all instances of namespace to correspond to your deployment. 
 
 1. Delete the Elasticsearch and Kibana resources using the following command:
 
@@ -27,4 +27,4 @@ If you are upgrading from July 22 (22.3.1) or earlier, to October 22 (22.4.1) or
 
 ### Deploy Elasticsearch and Kibana in centralized stack
 
-1. Follow [Install Elasticsearch stack and Kibana](../../manage-oam-domains/logging-and-visualization/#install-elasticsearch-stack-and-kibana) to deploy Elasticsearch and Kibana in a centralized stack.
+1. Follow [Install Elasticsearch stack and Kibana](../../manage-oam-domains/logging-and-visualization/#install-elasticsearch-stack-and-kibana) to deploy Elasticsearch and Kibana in a centralized stack.

docs-source/content/oig/patch-and-upgrade/upgrade-elk.md

@@ -19,7 +19,7 @@ Deployments prior to October 22 (22.4.1) used local deployments of Elasticsearch
 
 If you are upgrading from July 22 (22.3.1) or earlier, to October 22 (22.4.1) or later, you must first undeploy Elasticsearch and Kibana using the steps below:
 
-1. If your domain namespace is anything other than `oigns`, edit the `$WORKDIR/kubernetes/elasticsearch-and-kibana/elasticsearch_and_kibana.yaml` and change all instances of `namespace: "oigns"` to your domain namespace.
+1. Edit the `$WORKDIR/kubernetes/elasticsearch-and-kibana/elasticsearch_and_kibana.yaml` and change all instances of namespace to correspond to your deployment.
 
 1. Delete the Elasticsearch and Kibana resources using the following command:
 
@@ -29,4 +29,4 @@ If you are upgrading from July 22 (22.3.1) or earlier, to October 22 (22.4.1) or
 
 ### Deploy Elasticsearch and Kibana in centralized stack
 
-1. Follow [Install Elasticsearch stack and Kibana](../manage-oig-domains/logging-and-visualization/#install-elasticsearch-stack-and-kibana) to deploy Elasticsearch and Kibana in a centralized stack.
+1. Follow [Install Elasticsearch stack and Kibana](../../manage-oig-domains/logging-and-visualization/#install-elasticsearch-stack-and-kibana) to deploy Elasticsearch and Kibana in a centralized stack.

docs-source/content/oudsm/patch-and-upgrade/_index.md

@@ -1,7 +1,7 @@
 +++
 title = "Patch and upgrade"
-weight = 11 
-pre = "<b>11. </b>"
+weight = 8 
+pre = "<b>8. </b>"
 description=  "This document provides steps to patch or upgrade an OUD image, and Elasticsearch and Kibana."
 +++
 

docs-source/content/oudsm/patch-and-upgrade/upgrade-elk.md

@@ -76,4 +76,4 @@ If you are upgrading from July 22 (22.3.1) or earlier, to October 22 (22.4.1) or
 
 ### Deploy Elasticsearch and Kibana in centralized stack
 
-1. Follow [Install Elasticsearch stack and Kibana](../../manage-oudsm-containers/logging-and-visualization/#install-elasticsearch-stack-and-kibana) to deploy ElasticSearch and Kibana in a centralized stack.
+1. Follow [Install Elasticsearch stack and Kibana](../../manage-oudsm-containers/logging-and-visualization/#install-elasticsearch-stack-and-kibana) to deploy Elasticsearch and Kibana in a centralized stack.