changes related to subs=true

Author: shainaraskas

deploy-manage/deploy/cloud-on-k8s/install-using-yaml-manifest-quickstart.md

@@ -39,7 +39,7 @@ To deploy the ECK operator:
 
 1. Install Elastic's [custom resource definitions](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/) with [`create`](https://kubernetes.io/docs/reference/kubectl/generated/kubectl_create/):
 
-    ```sh
+    ```sh subs=true
     kubectl create -f https://download.elastic.co/downloads/eck/{{eck_version}}/crds.yaml
     ```
 
@@ -58,7 +58,7 @@ To deploy the ECK operator:
 
 2. Using [`kubectl apply`](https://kubernetes.io/docs/reference/kubectl/generated/kubectl_apply/), install the operator with its RBAC rules:
 
-    ```sh
+    ```sh subs=true
     kubectl apply -f https://download.elastic.co/downloads/eck/{{eck_version}}/operator.yaml
     ```
 

deploy-manage/deploy/cloud-on-k8s/k8s-openshift-deploy-operator.md

@@ -12,7 +12,7 @@ This page shows the installation steps to deploy ECK in Openshift:
 
 1. Apply the manifests the same way as described in [](./install-using-yaml-manifest-quickstart.md) document:
 
-   ```shell
+   ```shell subs=true
    oc create -f https://download.elastic.co/downloads/eck/{{eck_version}}/crds.yaml
    oc apply -f https://download.elastic.co/downloads/eck/{{eck_version}}/operator.yaml
    ```

deploy-manage/deploy/cloud-on-k8s/k8s-service-mesh-istio.md

@@ -35,7 +35,7 @@ The operator itself must be connected to the service mesh to deploy and manage E
 
 2. Install ECK:
 
-    ```sh
+    ```sh subs=true
     kubectl create -f https://download.elastic.co/downloads/eck/{{eck_version}}/crds.yaml
     kubectl apply -f https://download.elastic.co/downloads/eck/{{eck_version}}/operator.yaml
     ```

deploy-manage/deploy/cloud-on-k8s/k8s-service-mesh-linkerd.md

@@ -19,7 +19,7 @@ These instructions have been tested with Linkerd 2.7.0.
 
 In order to connect the operator to the service mesh, Linkerd sidecar must be injected into the ECK deployment. This can be done during installation as follows:
 
-```sh
+```sh subs=true
 kubectl create -f https://download.elastic.co/downloads/eck/{{eck_version}}/crds.yaml
 linkerd inject https://download.elastic.co/downloads/eck/{{eck_version}}/operator.yaml | kubectl apply -f -
 ```

deploy-manage/deploy/self-managed.md

@@ -1,8 +1,6 @@
 ---
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/dependencies-versions.html
-sub:
-  stack-version: "9.0.0"
 applies_to:
   deployment:
     self:

deploy-manage/deploy/self-managed/_snippets/ca-cert.md

@@ -1,6 +1,6 @@
 If your library doesn’t support a method of validating the fingerprint, the auto-generated CA certificate is created in the following directory on each {{es}} node:
 
-```sh
+```sh subs=true
 {{es-conf}}{{slash}}certs{{slash}}http_ca.crt
 ```
 

deploy-manage/deploy/self-managed/_snippets/ca-fingerprint.md

@@ -9,6 +9,6 @@ openssl x509 -fingerprint -sha256 -in config/certs/http_ca.crt
 The command returns the security certificate, including the fingerprint. The `issuer` should be `{{es}} security auto-configuration HTTP CA`.
 
 ```sh
-issuer= /CN={{es}} security auto-configuration HTTP CA
+issuer= /CN=Elasticsearch security auto-configuration HTTP CA
 SHA256 Fingerprint=<fingerprint>
 ```

deploy-manage/deploy/self-managed/_snippets/check-es-running.md

@@ -1,6 +1,6 @@
 You can test that your {{es}} node is running by sending an HTTPS request to port `9200` on `localhost`:
 
-```sh
+```sh subs=true
 curl --cacert {{es-conf}}{{slash}}certs{{slash}}http_ca.crt {{escape}} <1>
 -u elastic:$ELASTIC_PASSWORD https://localhost:9200 <2>
 ```

deploy-manage/deploy/self-managed/_snippets/cmd-line-config.md

@@ -2,13 +2,14 @@
 
 ```sh subs=true
 {{es-conf}}{{slash}}elasticsearch.yml
+```
 
 The format of this config file is explained in [](/deploy-manage/deploy/self-managed/configure-elasticsearch.md).
 
 Any settings that can be specified in the config file can also be specified on the command line, using the `-E` syntax as follows:
 
-```sh
-.\bin\elasticsearch.bat -Ecluster.name=my_cluster -Enode.name=node_1
+```sh subs=true
+.{{slash}}bin{{slash}}elasticsearch{{auto}} -Ecluster.name=my_cluster -Enode.name=node_1
 ```
 
 :::{note}

deploy-manage/deploy/self-managed/_snippets/connect-clients.md

@@ -3,7 +3,7 @@
 
 When you start {{es}} for the first time, TLS is configured automatically for the HTTP layer. A CA certificate is generated and stored on disk at:
 
-```sh
+```sh subs=true
 {{es-conf}}{{slash}}certs{{slash}}http_ca.crt
 ```