From 24f8ec395bbc8575b15061c42dfa93e3548fbe20 Mon Sep 17 00:00:00 2001
From: Rajesh Deshpande <rajesh.deshpande02@infosys.com>
Date: Sun, 15 Mar 2020 14:54:35 +0530
Subject: [PATCH] Correcting heading syntax (#19609)

Correcting heading syntax
---
 .../connecting-frontend-backend.md                     | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/content/en/docs/tasks/access-application-cluster/connecting-frontend-backend.md b/content/en/docs/tasks/access-application-cluster/connecting-frontend-backend.md
index 3cb90383c7..123271be44 100644
--- a/content/en/docs/tasks/access-application-cluster/connecting-frontend-backend.md
+++ b/content/en/docs/tasks/access-application-cluster/connecting-frontend-backend.md
@@ -39,7 +39,7 @@ frontend and backend are connected using a Kubernetes
 
 {{% capture lessoncontent %}}
 
-### Creating the backend using a Deployment
+## Creating the backend using a Deployment
 
 The backend is a simple hello greeter microservice. Here is the configuration
 file for the backend Deployment:
@@ -95,7 +95,7 @@ Events:
 ...
 ```
 
-### Creating the backend Service object
+## Creating the backend Service object
 
 The key to connecting a frontend to a backend is the backend
 Service. A Service creates a persistent IP address and DNS name entry
@@ -119,7 +119,7 @@ kubectl apply -f https://k8s.io/examples/service/access/hello-service.yaml
 At this point, you have a backend Deployment running, and you have a
 Service that can route traffic to it.
 
-### Creating the frontend
+## Creating the frontend
 
 Now that you have your backend, you can create a frontend that connects to the backend.
 The frontend connects to the backend worker Pods by using the DNS name
@@ -158,7 +158,7 @@ be to use a
 so that you can change the configuration more easily.
 {{< /note >}}
 
-### Interact with the frontend Service
+## Interact with the frontend Service
 
 Once you’ve created a Service of type LoadBalancer, you can use this
 command to find the external IP:
@@ -186,7 +186,7 @@ frontend   LoadBalancer   10.51.252.116   XXX.XXX.XXX.XXX    80/TCP   1m
 That IP can now be used to interact with the `frontend` service from outside the
 cluster.
 
-### Send traffic through the frontend
+## Send traffic through the frontend
 
 The frontend and backends are now connected. You can hit the endpoint
 by using the curl command on the external IP of your frontend Service.