Merge pull request #16531 from janetkuo/remove-red-rectangles

docs/user-guide/compute-resources.md

@@ -96,9 +96,9 @@ spec:
   - name: db
     image: mysql
     resources:
-	  requests:
-	    memory: "64Mi"
-		cpu: "250m"
+      requests:
+        memory: "64Mi"
+        cpu: "250m"
       limits:
         memory: "128Mi"
         cpu: "500m"
@@ -106,9 +106,9 @@ spec:
     image: wordpress
     resources:
       requests:
-	    memory: "64Mi"
-		cpu: "250m"
-	  limits:
+        memory: "64Mi"
+        cpu: "250m"
+      limits:
         memory: "128Mi"
         cpu: "500m"
 ```

docs/user-guide/production-pods.md

@@ -272,11 +272,11 @@ spec:
             cpu: 500m
             # memory units are bytes
             memory: 64Mi
-		  requests:
-			# cpu units are cores
-		    cpu: 500m
-			# memory units are bytes
-			memory: 64Mi
+          requests:
+            # cpu units are cores
+            cpu: 500m
+            # memory units are bytes
+            memory: 64Mi
 ```
 
 The container will die due to OOM (out of memory) if it exceeds its specified limit, so specifying a value a little higher than expected generally improves reliability. By specifying request, pod is guaranteed to be able to use that much of resource when needed. See [Resource QoS](../proposals/resource-qos.md) for the difference between resource limits and requests.