Toc docs reorg

docs/concepts_appid.md

@@ -1,10 +1,8 @@
 ---
-title: Application Identification
-sidebar_label: Application Identification
+title: Overview of Application Identification
+sidebar_label: Overview of Application Identification
 ---
 
-## Identifying Applications by Name
-
 The Session Smart Routing platform has several techniques by which it can associate inbound traffic to named applications. This is sometimes referred to as "Application Identification" (or "appID"), and the feature that allows administrators to define network policies using Fully Qualified Domain Names (FQDNs) instead of IP addresses.
 
 The SSR has three built-in techniques for affiliating named applications to services, all of which will be described in this document. (A fourth technique, involving service function chaining third party software is not covered here.) The three techniques are:

docs/concepts_pcli.md

@@ -1,10 +1,8 @@
 ---
-title: 'Programmable Command Line Interface (PCLI)'
-sidebar_label: 'PCLI'
+title: 'About the Programmable Command Line Interface (PCLI)'
+sidebar_label: 'About the PCLI'
 ---
 
-## About the PCLI
-
 The Programmable Command Line Interface (PCLI) is one of the two primary human interfaces for the SSR; this document uses the terms PCLI and CLI interchangeably. This document describes how to use the PCLI commands supported by the SSR. 
 
 Note that all of the examples in this document are run as the _admin_ role (as denoted by the prompt in this and other examples); however, each command also indicates which user roles – either _user_ or _admin_ at the time of this writing – are eligible to run the command based upon that command's privileges. Note that unprivileged _user_ accounts are not only unable to execute these commands, they do not "see" them in the PCLI as part of the help text, etc.

docs/config_app_ident.md

@@ -1,6 +1,6 @@
 ---
-title: Application Identification
-sidebar_label: Application Identification
+title: Configuring Application Identification
+sidebar_label: Configuring Application Identification
 ---
 
 Application Identification can automatically learn, identify, and classify applications processed by the SSR and store them in the [web filtering cache](config_domain-based_web_filter.md#how-it-works). 

docs/config_rate_limiting.md

@@ -1,5 +1,6 @@
 ---
 title: Rate Limiting
+sidebar_label: Rate Limiting
 ---
 
 Rate limiting, when configured, is applied to packets entering the data path prior to any packet transformations so as to prevent an individual flow from consuming more bandwidth than allowed.
@@ -104,7 +105,7 @@ exit
 
 ```
 
-### Troubleshooting
+## Troubleshooting
 
 To determine the number of packets meeting the rate limit check, execute the command on the PCLI:
 ```