Converges titles to imperative-form, front-matter based, and sentence-case (#438)

Multiple title fixes, consistency fixes, convergence into metadata-based titles.

docs/spec/api.md

@@ -2,14 +2,9 @@
 description: Specification for the Registry API.
 keywords:
 - registry, on-prem, images, tags, repository, distribution, api, advanced
-menu:
-  main:
-    parent: smn_registry_ref
-title: HTTP API V2
+title: Docker Registry HTTP API V2
 ---
 
-# Docker Registry HTTP API V2
-
 ## Introduction
 
 The _Docker Registry HTTP API_ is the protocol to facilitate distribution of

docs/spec/auth/index.md

@@ -2,15 +2,9 @@
 description: Docker Registry v2 authentication schema
 keywords:
 - registry, on-prem, images, tags, repository, distribution, authentication, advanced
-menu:
-  main:
-    parent: smn_registry_ref
-    weight: 100
-title: Docker Registry Token Authentication
+title: Docker Registry v2 authentication
 ---
 
-# Docker Registry v2 authentication
-
 See the [Token Authentication Specification](token.md),
 [Token Authentication Implementation](jwt.md),
 [Token Scope Documentation](scope.md),

docs/spec/auth/jwt.md

@@ -1,17 +1,10 @@
 ---
-description: Describe the reference implementation of the Docker Registry v2 authentication
-  schema
+description: Describe the reference implementation of the Docker Registry v2 authentication schema
 keywords:
 - registry, on-prem, images, tags, repository, distribution, JWT authentication, advanced
-menu:
-  main:
-    parent: smn_registry_ref
-    weight: 101
-title: Token Authentication Implementation
+title: Docker Registry v2 Bearer token specification
 ---
 
-# Docker Registry v2 Bearer token specification
-
 This specification covers the `docker/distribution` implementation of the
 v2 Registry's authentication schema.  Specifically, it describes the JSON
 Web Token schema that `docker/distribution` has adopted to implement the

docs/spec/auth/oauth.md

@@ -2,15 +2,9 @@
 description: Specifies the Docker Registry v2 authentication
 keywords:
 - registry, on-prem, images, tags, repository, distribution, oauth2, advanced
-menu:
-  main:
-    parent: smn_registry_ref
-    weight: 102
-title: Oauth2 Token Authentication
+title: Docker Registry v2 authentication using OAuth2
 ---
 
-# Docker Registry v2 authentication using OAuth2
-
 This document describes support for the OAuth2 protocol within the authorization
 server. [RFC6749](https://tools.ietf.org/html/rfc6749) should be used as a
 reference for the protocol and HTTP endpoints described here.
@@ -188,4 +182,3 @@ Content-Type: application/json
 
 {"refresh_token":"kas9Da81Dfa8","access_token":"eyJhbGciOiJFUzI1NiIsInR5":"expires_in":900,"scope":"repository:samalba/my-app:pull,repository:samalba/my-app:push"}
 ```
-

docs/spec/auth/scope.md

@@ -1,17 +1,10 @@
 ---
-description: Describes the scope and access fields used for registry authorization
-  tokens
+description: Describes the scope and access fields used for registry authorization tokens
 keywords:
 - registry, on-prem, images, tags, repository, distribution, advanced, access, scope
-menu:
-  main:
-    parent: smn_registry_ref
-    weight: 103
-title: Token Scope Documentation
+title: Docker Registry token scope and access
 ---
 
-# Docker Registry Token Scope and Access
-
 Tokens used by the registry are always restricted what resources they may
 be used to access, where those resources may be accessed, and what actions
 may be done on those resources. Tokens always have the context of a user which
@@ -141,4 +134,3 @@ done by fetching an access token using the refresh token. Since the refresh
 token is not scoped to specific resources for an audience, extra care should
 be taken to only use the refresh token to negotiate new access tokens directly
 with the authorization server, and never with a resource provider.
-

docs/spec/auth/token.md

@@ -1,17 +1,10 @@
 ---
 description: Specifies the Docker Registry v2 authentication
 keywords:
-- registry, on-prem, images, tags, repository, distribution, Bearer authentication,
-  advanced
-menu:
-  main:
-    parent: smn_registry_ref
-    weight: 104
-title: Token Authentication Specification
+- registry, on-prem, images, tags, repository, distribution, Bearer authentication, advanced
+title: Docker Registry v2 authentication via central service
 ---
 
-# Docker Registry v2 authentication via central service
-
 This document outlines the v2 Docker registry authentication scheme:
 
 ![v2 registry auth](../../images/v2-registry-auth.png)
@@ -26,7 +19,7 @@ This document outlines the v2 Docker registry authentication scheme:
 5. The client retries the original request with the Bearer token embedded in
    the request's Authorization header.
 6. The Registry authorizes the client by validating the Bearer token and the
-   claim set embedded within it and begins the push/pull session as usual. 
+   claim set embedded within it and begins the push/pull session as usual.
 
 ## Requirements
 
@@ -82,7 +75,8 @@ Note the HTTP Response Header indicating the auth challenge:
 Www-Authenticate: Bearer realm="https://auth.docker.io/token",service="registry.docker.io",scope="repository:samalba/my-app:pull,push"
 ```
 
-This format is documented in [Section 3 of RFC 6750: The OAuth 2.0 Authorization Framework: Bearer Token Usage](https://tools.ietf.org/html/rfc6750#section-3)
+This format is documented in [Section 3 of RFC 6750: The OAuth 2.0 Authorization
+Framework: Bearer Token Usage](https://tools.ietf.org/html/rfc6750#section-3)
 
 This challenge indicates that the registry requires a token issued by the
 specified token server and that the request the client is attempting will
@@ -162,7 +156,7 @@ Defines getting a bearer and refresh token using the token endpoint.
         <code>expires_in</code>
     </dt>
     <dd>
-        (Optional) The duration in seconds since the token was issued that it 
+        (Optional) The duration in seconds since the token was issued that it
         will remain valid.  When omitted, this defaults to 60 seconds.  For
         compatibility with older clients, a token should never be returned with
         less than 60 seconds to live.
@@ -253,4 +247,5 @@ token placed in the HTTP `Authorization` header like so:
 Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJFUzI1NiIsImtpZCI6IkJWM0Q6MkFWWjpVQjVaOktJQVA6SU5QTDo1RU42Ok40SjQ6Nk1XTzpEUktFOkJWUUs6M0ZKTDpQT1RMIn0.eyJpc3MiOiJhdXRoLmRvY2tlci5jb20iLCJzdWIiOiJCQ0NZOk9VNlo6UUVKNTpXTjJDOjJBVkM6WTdZRDpBM0xZOjQ1VVc6NE9HRDpLQUxMOkNOSjU6NUlVTCIsImF1ZCI6InJlZ2lzdHJ5LmRvY2tlci5jb20iLCJleHAiOjE0MTUzODczMTUsIm5iZiI6MTQxNTM4NzAxNSwiaWF0IjoxNDE1Mzg3MDE1LCJqdGkiOiJ0WUpDTzFjNmNueXk3a0FuMGM3cktQZ2JWMUgxYkZ3cyIsInNjb3BlIjoiamxoYXduOnJlcG9zaXRvcnk6c2FtYWxiYS9teS1hcHA6cHVzaCxwdWxsIGpsaGF3bjpuYW1lc3BhY2U6c2FtYWxiYTpwdWxsIn0.Y3zZSwaZPqy4y9oRBVRImZyv3m_S9XDHF1tWwN7mL52C_IiA73SJkWVNsvNqpJIn5h7A2F8biv_S2ppQ1lgkbw
 ```
 
-This is also described in [Section 2.1 of RFC 6750: The OAuth 2.0 Authorization Framework: Bearer Token Usage](https://tools.ietf.org/html/rfc6750#section-2.1)
+This is also described in [Section 2.1 of RFC 6750: The OAuth 2.0 Authorization
+Framework: Bearer Token Usage](https://tools.ietf.org/html/rfc6750#section-2.1)

docs/spec/index.md

@@ -2,15 +2,9 @@
 description: Explains registry JSON objects
 keywords:
 - registry, service, images, repository,  json
-menu:
-  main:
-    parent: smn_registry_ref
-    weight: -1
-title: Reference Overview
+title: Docker Registry Reference
 ---
 
-# Docker Registry Reference
-
 * [HTTP API V2](api.md)
 * [Storage Driver](../storage-drivers/index.md)
 * [Token Authentication Specification](auth/token.md)

docs/spec/json.md

@@ -3,14 +3,9 @@ description: Explains registry JSON objects
 published: false
 keywords:
 - registry, service, images, repository,  json
-menu:
-  main:
-    parent: smn_registry_ref
-title: Docker Distribution JSON Canonicalization
+title: Docker Distribution JSON canonicalization
 ---
 
-# Docker Distribution JSON Canonicalization
-
 To provide consistent content hashing of JSON objects throughout Docker
 Distribution APIs, the specification defines a canonical JSON format. Adopting
 such a canonicalization also aids in caching JSON responses.

docs/spec/manifest-v2-1.md

@@ -2,14 +2,9 @@
 description: image manifest for the Registry.
 keywords:
 - registry, on-prem, images, tags, repository, distribution, api, advanced, manifest
-menu:
-  main:
-    parent: smn_registry_ref
-title: 'Image Manifest V 2, Schema 1 '
+title: Image manifest V2, schema 1
 ---
 
-# Image Manifest Version 2, Schema 1
-
 This document outlines the format of of the V2 image manifest. The image
 manifest described herein was introduced in the Docker daemon in the [v1.3.0
 release](https://github.com/docker/docker/commit/9f482a66ab37ec396ac61ed0c00d59122ac07453).

docs/spec/manifest-v2-2.md

@@ -2,14 +2,9 @@
 description: image manifest for the Registry.
 keywords:
 - registry, on-prem, images, tags, repository, distribution, api, advanced, manifest
-menu:
-  main:
-    parent: smn_registry_ref
-title: 'Image Manifest V 2, Schema 2 '
+title: Image manifest V2, schema 2
 ---
 
-# Image Manifest Version 2, Schema 2
-
 This document outlines the format of of the V2 image manifest, schema version 2.
 The original (and provisional) image manifest for V2 (schema 1), was introduced
 in the Docker daemon in the [v1.3.0