Reduce heading levels by 1.

docs/tutorials/stateless-application/hello-minikube.md

@@ -38,7 +38,7 @@ driver.
 
 {% capture lessoncontent %}
 
-### Create a Minikube cluster
+## Create a Minikube cluster
 
 This tutorial uses [Minikube](https://github.com/kubernetes/minikube) to
 create a local cluster. This tutorial also assumes you are using
@@ -94,7 +94,7 @@ Verify that `kubectl` is configured to communicate with your cluster:
 kubectl cluster-info
 ```
 
-### Create your Node.js application
+## Create your Node.js application
 
 The next step is to write the application. Save this code in a folder named `hellonode`
 with the filename `server.js`:
@@ -113,7 +113,7 @@ Stop the running Node.js server by pressing **Ctrl-C**.
 
 The next step is to package your application in a Docker container.
 
-### Create a Docker container image
+## Create a Docker container image
 
 Create a file, also in the `hellonode` folder, named `Dockerfile`. A Dockerfile describes
 the image that you want to build. You can build a Docker container image by extending an
@@ -145,7 +145,7 @@ docker build -t hello-node:v1 .
 
 Now the Minikube VM can run the image you built.
 
-### Create a Deployment
+## Create a Deployment
 
 A Kubernetes [*Pod*](/docs/user-guide/pods/) is a group of one or more Containers,
 tied together for the purposes of administration and networking. The Pod in this
@@ -206,7 +206,7 @@ kubectl config view
 For more information about `kubectl`commands, see the
 [kubectl overview](/docs/user-guide/kubectl-overview/).
 
-### Create a Service
+## Create a Service
 
 By default, the Pod is only accessible by its internal IP address within the
 Kubernetes cluster. To make the `hello-node` Container accessible from outside the
@@ -254,7 +254,7 @@ you should now be able to see some logs:
 kubectl logs <POD-NAME>
 ```
 
-### Update your app
+## Update your app
 
 Edit your `server.js` file to return a new message:
 
@@ -281,7 +281,7 @@ Run your app again to view the new message:
 minikube service hello-node
 ```
 
-### Clean up
+## Clean up
 
 Now you can clean up the resources you created in your cluster: