Remove data-lang for command outputs

content/en/docs/concepts/services-networking/dns-pod-service.md

@@ -307,7 +307,7 @@ For IPv6 setup, search path and name server should be setup like this:
 kubectl exec -it dns-example -- cat /etc/resolv.conf
 ```
 The output is similar to this:
-```shell
+```
 nameserver fd00:79:30::a
 search default.svc.cluster-domain.example svc.cluster-domain.example cluster-domain.example
 options ndots:5

content/en/docs/concepts/workloads/controllers/job.md

@@ -119,7 +119,7 @@ kubectl logs $pods
 
 The output is similar to this:
 
-```shell
+```
 3.1415926535897932384626433832795028841971693993751058209749445923078164062862089986280348253421170679821480865132823066470938446095505822317253594081284811174502841027019385211055596446229489549303819644288109756659334461284756482337867831652712019091456485669234603486104543266482133936072602491412737245870066063155881748815209209628292540917153643678925903600113305305488204665213841469519415116094330572703657595919530921861173819326117931051185480744623799627495673518857527248912279381830119491298336733624406566430860213949463952247371907021798609437027705392171762931767523846748184676694051320005681271452635608277857713427577896091736371787214684409012249534301465495853710507922796892589235420199561121290219608640344181598136297747713099605187072113499999983729780499510597317328160963185950244594553469083026425223082533446850352619311881710100031378387528865875332083814206171776691473035982534904287554687311595628638823537875937519577818577805321712268066130019278766111959092164201989380952572010654858632788659361533818279682303019520353018529689957736225994138912497217752834791315155748572424541506959508295331168617278558890750983817546374649393192550604009277016711390098488240128583616035637076601047101819429555961989467678374494482553797747268471040475346462080466842590694912933136770289891521047521620569660240580381501935112533824300355876402474964732639141992726042699227967823547816360093417216412199245863150302861829745557067498385054945885869269956909272107975093029553211653449872027559602364806654991198818347977535663698074265425278625518184175746728909777727938000816470600161452491921732172147723501414419735685481613611573525521334757418494684385233239073941433345477624168625189835694855620992192221842725502542568876717904946016534668049886272327917860857843838279679766814541009538837863609506800642251252051173929848960841284886269456042419652850222106611863067442786220391949450471237137869609563643719172874677646575739624138908658326459958133904780275901
 ```
 

content/en/docs/concepts/workloads/controllers/replicaset.md

@@ -78,7 +78,7 @@ kubectl describe rs/frontend
 
 And you will see output similar to:
 
-```shell
+```
 Name:         frontend
 Namespace:    default
 Selector:     tier=frontend
@@ -130,7 +130,7 @@ kubectl get pods frontend-b2zdv -o yaml
 
 The output will look similar to this, with the frontend ReplicaSet's info set in the metadata's ownerReferences field:
 
-```shell
+```yaml
 apiVersion: v1
 kind: Pod
 metadata:
@@ -181,7 +181,7 @@ kubectl get pods
 
 The output shows that the new Pods are either already terminated, or in the process of being terminated:
 
-```shell
+```
 NAME             READY   STATUS        RESTARTS   AGE
 frontend-b2zdv   1/1     Running       0          10m
 frontend-vcmts   1/1     Running       0          10m
@@ -210,7 +210,7 @@ kubectl get pods
 ```
 
 Will reveal in its output:
-```shell
+```
 NAME             READY   STATUS    RESTARTS   AGE
 frontend-hmmj2   1/1     Running   0          9s
 pod1             1/1     Running   0          36s

content/en/docs/tasks/access-application-cluster/configure-access-multiple-clusters.md

@@ -115,7 +115,7 @@ kubectl config --kubeconfig=config-demo view
 
 The output shows the two clusters, two users, and three contexts:
 
-```shell
+```yaml
 apiVersion: v1
 clusters:
 - cluster:

content/en/docs/tasks/administer-cluster/quota-api-object.md

@@ -89,7 +89,7 @@ kubectl get persistentvolumeclaims --namespace=quota-object-example
 
 The output shows that the PersistentVolumeClaim exists and has status Pending:
 
-```shell
+```
 NAME             STATUS
 pvc-quota-demo   Pending
 ```

content/en/docs/tasks/configure-pod-container/assign-memory-resource.md

@@ -171,7 +171,7 @@ kubectl get pod memory-demo-2 --output=yaml --namespace=mem-example
 
 The output shows that the Container was killed because it is out of memory (OOM):
 
-```shell
+```yaml
 lastState:
    terminated:
      containerID: 65183c1877aaec2e8427bc95609cc52677a454b56fcb24340dbd22917c23b10f
@@ -278,7 +278,7 @@ kubectl describe pod memory-demo-3 --namespace=mem-example
 
 The output shows that the Container cannot be scheduled because of insufficient memory on the Nodes:
 
-```shell
+```
 Events:
   ...  Reason            Message
        ------            -------
@@ -291,8 +291,8 @@ The memory resource is measured in bytes. You can express memory as a plain inte
 fixed-point integer with one of these suffixes: E, P, T, G, M, K, Ei, Pi, Ti, Gi, Mi, Ki.
 For example, the following represent approximately the same value:
 
-```shell
-128974848, 129e6, 129M , 123Mi
+```
+128974848, 129e6, 129M, 123Mi
 ```
 
 Delete your Pod:

content/en/docs/tasks/configure-pod-container/configure-pod-configmap.md

@@ -548,7 +548,7 @@ kubectl create -f https://kubernetes.io/examples/pods/pod-configmap-env-var-valu
 
 produces the following output in the `test-container` container:
 
-```shell
+```
 very charm
 ```
 
@@ -582,7 +582,7 @@ kubectl create -f https://kubernetes.io/examples/pods/pod-configmap-volume.yaml
 
 When the pod runs, the command `ls /etc/config/` produces the output below:
 
-```shell
+```
 SPECIAL_LEVEL
 SPECIAL_TYPE
 ```
@@ -610,7 +610,7 @@ kubectl create -f https://kubernetes.io/examples/pods/pod-configmap-volume-speci
 
 When the pod runs, the command `cat /etc/config/keys` produces the output below:
 
-```shell
+```
 very
 ```
 

content/en/docs/tasks/configure-pod-container/configure-runasusername.md

@@ -57,7 +57,7 @@ echo $env:USERNAME
 
 The output should be:
 
-```shell
+```
 ContainerUser
 ```
 
@@ -97,7 +97,7 @@ echo $env:USERNAME
 
 The output should be:
 
-```shell
+```
 ContainerAdministrator
 ```
 

content/en/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information.md

@@ -69,7 +69,7 @@ kubectl logs kubernetes-downwardapi-volume-example
 
 The output shows the contents of the `labels` file and the `annotations` file:
 
-```shell
+```
 cluster="test-cluster1"
 rack="rack-22"
 zone="us-est-coast"

content/en/docs/tasks/manage-daemon/update-daemon-set.md

@@ -79,7 +79,7 @@ kubectl apply -f https://k8s.io/examples/controllers/fluentd-daemonset.yaml --dr
 
 The output from both commands should be:
 
-```shell
+```
 RollingUpdate
 ```
 

content/en/docs/tasks/manage-kubernetes-objects/update-api-object-kubectl-patch.md

@@ -82,7 +82,7 @@ kubectl get deployment patch-demo --output yaml
 
 The output shows that the PodSpec in the Deployment has two Containers:
 
-```shell
+```yaml
 containers:
 - image: redis
   imagePullPolicy: Always
@@ -309,7 +309,7 @@ kubectl patch deployment retainkeys-demo --type merge --patch-file patch-file-no
 
 In the output, you can see that it is not possible to set `type` as `Recreate` when a value is defined for `spec.strategy.rollingUpdate`:
 
-```shell
+```
 The Deployment "retainkeys-demo" is invalid: spec.strategy.rollingUpdate: Forbidden: may not be specified when strategy `type` is 'Recreate'
 ```
 
@@ -341,7 +341,7 @@ kubectl get deployment retainkeys-demo --output yaml
 
 The output shows that the strategy object in the Deployment does not contain the `rollingUpdate` key anymore:
 
-```shell
+```yaml
 spec:
   strategy:
     type: Recreate

content/en/docs/tutorials/configuration/configure-redis-using-configmap.md

@@ -78,7 +78,7 @@ kubectl get pod/redis configmap/example-redis-config
 
 You should see the following output:
 
-```shell
+```
 NAME        READY   STATUS    RESTARTS   AGE
 pod/redis   1/1     Running   0          8s