fix page formatting

content/en/docs/concepts/cluster-administration/flow-control.md

@@ -18,12 +18,12 @@ potentially crashing the API server, but these flags are not enough to ensure
 that the most important requests get through in a period of high traffic.
 
 The API Priority and Fairness feature (APF) is an alternative that improves upon
-aforementioned max-inflight limitations.  APF classifies
+aforementioned max-inflight limitations. APF classifies
-and isolates requests in a more fine-grained way.  It also introduces
+and isolates requests in a more fine-grained way. It also introduces
 a limited amount of queuing, so that no requests are rejected in cases
 of very brief bursts.  Requests are dispatched from queues using a
-fair queuing technique so that, for example, a poorly-behaved {{<
+fair queuing technique so that, for example, a poorly-behaved
-glossary_tooltip text="controller" term_id="controller" >}}) need not
+{{< glossary_tooltip text="controller" term_id="controller" >}} need not
 starve others (even at the same priority level).
 
 {{< caution >}}

content/en/docs/tasks/setup-konnectivity/setup-konnectivity.md

@@ -1,30 +1,43 @@
 ---
-title: Setup Konnectivity Service 
+title: Set up Konnectivity service
 content_template: templates/task
-weight: 110
+weight: 70
 ---
 
+{{% capture overview %}}
+
 The Konnectivity service provides TCP level proxy for the Master → Cluster
 communication.
 
-You can set it up with the following steps.
+{{% /capture %}}
+
+{{% capture prerequisites %}}
+
+{{< include "task-tutorial-prereqs.md" >}}
+
+{{% /capture %}}
+
+{{% capture steps %}}
+
+## Configure the Konnectivity service
 
 First, you need to configure the API Server to use the Konnectivity service
 to direct its network traffic to cluster nodes:
+
 1. Set the `--egress-selector-config-file` flag of the API Server, it is the
 path to the API Server egress configuration file.
-2. At the path, create a configuration file. For example,
+1. At the path, create a configuration file. For example,
 
 {{< codenew file="admin/konnectivity/egress-selector-configuration.yaml" >}}
 
-Next, you need to deploy the Konnectivity service server and agents.
+Next, you need to deploy the Konnectivity server and agents.
 [kubernetes-sigs/apiserver-network-proxy](https://github.com/kubernetes-sigs/apiserver-network-proxy)
 is a reference implementation.
 
-Deploy the Konnectivity server on your master node. The provided yaml assuming
+Deploy the Konnectivity server on your master node. The provided yaml assumes
-Kubernetes components are deployed as {{< glossary_tooltip text="static pod"
+that the Kubernetes components are deployed as a {{< glossary_tooltip text="static Pod"
-term_id="static-pod" >}} in your cluster. If not , you can deploy it as a
+term_id="static-pod" >}} in your cluster. If not, you can deploy the Konnectivity
-Daemonset to be reliable.
+server as a DaemonSet.
 
 {{< codenew file="admin/konnectivity/konnectivity-server.yaml" >}}
 
@@ -35,3 +48,5 @@ Then deploy the Konnectivity agents in your cluster:
 Last, if RBAC is enabled in your cluster, create the relevant RBAC rules:
 
 {{< codenew file="admin/konnectivity/konnectivity-rbac.yaml" >}}
+
+{{% /capture %}}