Fix title and add a TOC to the logging concept page

docs/concepts/cluster-administration/logging.md

@@ -2,7 +2,7 @@
 assignees:
 - crassirostris
 - piosz
-title: Logging and Monitoring Cluster Activity
+title: Logging Architecture
 redirect_from:
 - "/docs/concepts/clusters/logging/"
 - "/docs/concepts/clusters/logging.html"
@@ -15,13 +15,13 @@ Application and systems logs can help you understand what is happening inside yo
 
 However, the native functionality provided by a container engine or runtime is usually not enough for a complete logging solution. For example, if a container crashes, a pod is evicted, or a node dies, you'll usually still want to access your application's logs. As such, logs should have a separate storage and lifecycle independent of nodes, pods, or containers. This concept is called _cluster-level-logging_. Cluster-level logging requires a separate backend to store, analyze, and query logs. Kubernetes provides no native storage solution for log data, but you can integrate many existing logging solutions into your Kubernetes cluster.
 
-This document includes:
+* TOC
+{:toc}
 
-* A basic demonstration of logging in Kubernetes using the standard output stream
-* A detailed description of the node logging architecture in Kubernetes
-* Guidance for implementing cluster-level logging in Kubernetes
-
-The guidance for cluster-level logging assumes that a logging backend is present inside or outside of your cluster. If you're not interested in having cluster-level logging, you might still find the description of how logs are stored and handled on the node to be useful.
+Cluster-level logging architectures are described in assumption that
+a logging backend is present inside or outside of your cluster. If you're
+not interested in having cluster-level logging, you might still find
+the description of how logs are stored and handled on the node to be useful.
 
 ## Basic logging in Kubernetes