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

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

_layouts/docs.html

@@ -185,6 +185,7 @@ ng\:form {
             </div>
             <div {% if page.notoc %} class="col-xs-12 col-sm-9 col-md-10" {% else %} class="col-xs-12 col-sm-9 col-md-8 col-xl-9" {% endif %} >
               <section class="section" id="DocumentationText">
+								{% if page.title %}<h1>{{ page.title }}</h1>{% endif %}
               {{ content }}
 							{% if page.noratings != true %}
 							<div style="text-align: center; margin-top: 50px">

apidocs/index.md

@@ -2,17 +2,9 @@
 description: Learn how to use DTR APIs.
 keywords:
 - docker, registry, DTR, APIs
-menu:
-  main:
-    identifier: smn_dtrapi
-    parent: workw_dtr
-    weight: "100"
 title: DTR APIs
-type: _default
 ---
 
-# DTR APIs
-
 This section includes the following topics:
 
 * [API overview](overview.md)

apidocs/overview.md

@@ -2,17 +2,9 @@
 description: Learn how to use DTR APIs.
 keywords:
 - docker, registry, DTR, APIs
-menu:
-  main:
-    identifier: dtr_api_overview
-    parent: smn_dtrapi
-    weight: 0
-title: Overview
-type: _default
+title: API overview
 ---
 
-# API Overview
-
 Docker Trusted Registry has an experimental API that you can use to manage
 DTR repositories, permissions, and settings.
 

compose/bundles.md

@@ -1,17 +1,11 @@
 ---
 advisory: experimental
-description: Description of Docker and Compose's experimental support for application
-  bundles
+description: Description of Docker and Compose's experimental support for application bundles
 keywords:
 - documentation, docs,  docker, compose, bundles, stacks
-menu:
-  main:
-    parent: workw_compose
-title: Docker Stacks and Distributed Application Bundles
+title: Docker stacks and distributed application bundles (experimental)
 ---
 
-# Docker Stacks and Distributed Application Bundles (experimental)
-
 > **Note**: This is a copy of the [Docker Stacks and Distributed Application
 > Bundles](https://github.com/docker/docker/blob/v1.12.0-rc4/experimental/docker-stacks-and-bundles.md)
 > document in the [docker/docker repo](https://github.com/docker/docker).

compose/completion.md

@@ -2,15 +2,9 @@
 description: Compose CLI reference
 keywords:
 - fig, composition, compose, docker, orchestration, cli,  reference
-menu:
-  main:
-    parent: workw_compose
-    weight: 88
-title: Command-line Completion
+title: Command-line completion
 ---
 
-# Command-line Completion
-
 Compose comes with [command completion](http://en.wikipedia.org/wiki/Command-line_completion)
 for the bash and zsh shell.
 

compose/compose-file.md

@@ -4,15 +4,9 @@ aliases:
 description: Compose file reference
 keywords:
 - fig, composition, compose, docker
-menu:
-  main:
-    parent: workw_compose
-    weight: 70
-title: Compose File Reference
+title: Compose file reference
 ---
 
-# Compose file reference
-
 The Compose file is a [YAML](http://yaml.org/) file defining
 [services](compose-file.md#service-configuration-reference),
 [networks](compose-file.md#network-configuration-reference) and

compose/django.md

@@ -2,15 +2,9 @@
 description: Getting started with Docker Compose and Django
 keywords:
 - documentation, docs,  docker, compose, orchestration, containers
-menu:
-  main:
-    parent: workw_compose
-    weight: 4
-title: 'Quickstart: Compose and Django'
+title: "Quickstart: Compose and Django"
 ---
 
-# Quickstart: Docker Compose and Django
-
 This quick-start guide demonstrates how to use Docker Compose to set up and run a simple Django/PostgreSQL app. Before starting, you'll need to have
 [Compose installed](install.md).
 

compose/env-file.md

@@ -1,16 +1,10 @@
 ---
-description: Declaring default environment variables in file
+description: Declare default environment variables in a file
 keywords:
 - fig, composition, compose, docker, orchestration, environment, env file
-menu:
-  main:
-    parent: workw_compose
-    weight: 10
-title: Environment file
+title: Declare default environment variables in file
 ---
 
-# Environment file
-
 Compose supports declaring default environment variables in an environment
 file named `.env` placed in the folder `docker-compose` command is executed from
 *(current working directory)*.

compose/environment-variables.md

@@ -2,15 +2,9 @@
 description: How to set, use and manage environment variables in Compose
 keywords:
 - fig, composition, compose, docker, orchestration, environment, variables, env file
-menu:
-  main:
-    parent: workw_compose
-    weight: 10
 title: Environment variables in Compose
 ---
 
-# Environment variables in Compose
-
 There are multiple parts of Compose that deal with environment variables in one sense or another. This page should help you find the information you need.
 
 

compose/extends.md

@@ -1,17 +1,10 @@
 ---
-description: How to use Docker Compose's extends keyword to share configuration between
-  files and projects
+description: How to use Docker Compose's extends keyword to share configuration between files and projects
 keywords:
 - fig, composition, compose, docker, orchestration, documentation, docs
-menu:
-  main:
-    parent: workw_compose
-    weight: 20
-title: Extending Services in Compose
+title: Share Compose configurations between files and projects
 ---
 
-# Extending services and Compose files
-
 Compose supports two methods of sharing common configuration:
 
 1. Extending an entire Compose file by

compose/faq.md

@@ -1,16 +1,9 @@
 ---
 description: Docker Compose FAQ
 keywords: documentation, docs,  docker, compose, faq
-menu:
-  main:
-    identifier: faq.compose
-    parent: workw_compose
-    weight: 90
-title: Frequently Asked Questions
+title: Frequently asked questions
 ---
 
-# Frequently asked questions
-
 If you don’t see your question here, feel free to drop by `#docker-compose` on
 freenode IRC and ask the community.
 

compose/gettingstarted.md

@@ -1,16 +1,10 @@
 ---
-description: Getting started with Docker Compose
+description: Get started with Docker Compose
 keywords:
 - documentation, docs,  docker, compose, orchestration, containers
-menu:
-  main:
-    parent: workw_compose
-    weight: -85
-title: Getting Started
+title: Get started with Docker Compose
 ---
 
-# Getting Started
-
 On this page you build a simple Python web application running on Docker Compose. The
 application uses the Flask framework and increments a value in Redis. While the
 sample uses Python, the concepts demonstrated here should be understandable even

compose/index.md

@@ -2,15 +2,9 @@
 description: Introduction and Overview of Compose
 keywords:
 - documentation, docs,  docker, compose, orchestration,  containers
-menu:
-  main:
-    identifier: workw_compose
-    weight: -70
 title: Docker Compose
 ---
 
-# Docker Compose
-
 Compose is a tool for defining and running multi-container Docker applications. To learn more about Compose refer to the following documentation:
 
 - [Compose Overview](overview.md)

compose/install.md

@@ -2,15 +2,9 @@
 description: How to install Docker Compose
 keywords:
 - compose, orchestration, install, installation, docker, documentation
-menu:
-  main:
-    parent: workw_compose
-    weight: -90
-title: Install Compose
+title: Install Docker Compose
 ---
 
-# Install Docker Compose
-
 You can run Compose on macOS, Windows and 64-bit Linux. To install it, you'll need to install Docker first.
 
 To install Compose, do the following:

compose/link-env-deprecated.md

@@ -4,15 +4,9 @@ aliases:
 description: Compose CLI reference
 keywords:
 - fig, composition, compose, docker, orchestration, cli,  reference
-menu:
-  main:
-    parent: workw_compose
-    weight: 89
-title: Link Environment Variables
+title: Link environment variables (superseded)
 ---
 
-# Link environment variables reference
-
 > **Note:** Environment variables are no longer the recommended method for connecting to linked services. Instead, you should use the link name (by default, the name of the linked service) as the hostname to connect to. See the [docker-compose.yml documentation](compose-file.md#links) for details.
 >
 > Environment variables will only be populated if you're using the [legacy version 1 Compose file format](compose-file.md#versioning).

compose/networking.md

@@ -2,15 +2,9 @@
 description: How Compose sets up networking between containers
 keywords:
 - documentation, docs,  docker, compose, orchestration, containers, networking
-menu:
-  main:
-    parent: workw_compose
-    weight: 21
 title: Networking in Compose
 ---
 
-# Networking in Compose
-
 > **Note:** This document only applies if you're using [version 2 of the Compose file format](compose-file.md#versioning). Networking features are not supported for version 1 (legacy) Compose files.
 
 By default Compose sets up a single

compose/overview.md

@@ -2,15 +2,9 @@
 description: Introduction and Overview of Compose
 keywords:
 - documentation, docs,  docker, compose, orchestration,  containers
-menu:
-  main:
-    parent: workw_compose
-    weight: -99
 title: Overview of Docker Compose
 ---
 
-# Overview of Docker Compose
-
 Compose is a tool for defining and running multi-container Docker applications.
 With Compose, you use a Compose file to configure your application's services.
 Then, using a single command, you create and start all the services

compose/production.md

@@ -2,15 +2,9 @@
 description: Guide to using Docker Compose in production
 keywords:
 - documentation, docs,  docker, compose, orchestration, containers,  production
-menu:
-  main:
-    parent: workw_compose
-    weight: 22
-title: Using Compose in Production
+title: Using Compose in production
 ---
 
-## Using Compose in production
-
 When you define your app with Compose in development, you can use this
 definition to run your application in different environments such as CI,
 staging, and production.

compose/rails.md

@@ -2,15 +2,9 @@
 description: Getting started with Docker Compose and Rails
 keywords:
 - documentation, docs,  docker, compose, orchestration, containers
-menu:
-  main:
-    parent: workw_compose
-    weight: 5
-title: 'Quickstart: Compose and Rails'
+title: "Quickstart: Compose and Rails"
 ---
 
-## Quickstart: Docker Compose and Rails
-
 This Quickstart guide will show you how to use Docker Compose to set up and run a Rails/PostgreSQL app. Before starting, you'll need to have [Compose installed](install.md).
 
 ### Define the project

compose/reference/build.md

@@ -1,16 +1,10 @@
 ---
-description: build
+description: docker-compose build
 keywords:
 - fig, composition, compose, docker, orchestration, cli,  build
-menu:
-  main:
-    identifier: build.compose
-    parent: smn_compose_cli
-title: build
+title: docker-compose build
 ---
 
-# build
-
 ```
 Usage: build [options] [SERVICE...]
 

compose/reference/bundle.md

@@ -2,15 +2,9 @@
 description: Create a distributed application bundle from the Compose file.
 keywords:
 - fig, composition, compose, docker, orchestration, cli,  bundle
-menu:
-  main:
-    identifier: bundle.compose
-    parent: smn_compose_cli
-title: bundle
+title: docker-compose bundle
 ---
 
-# bundle
-
 ```
 Usage: bundle [options]
 

compose/reference/config.md

@@ -2,15 +2,9 @@
 description: Config validates and view the compose file.
 keywords:
 - fig, composition, compose, docker, orchestration, cli, config
-menu:
-  main:
-    identifier: config.compose
-    parent: smn_compose_cli
-title: config
+title: docker-compose config
 ---
 
-# config
-
 ```:
 Usage: config [options]
 

compose/reference/create.md

@@ -2,15 +2,9 @@
 description: Create creates containers for a service.
 keywords:
 - fig, composition, compose, docker, orchestration, cli, create
-menu:
-  main:
-    identifier: create.compose
-    parent: smn_compose_cli
-title: create
+title: docker-compose create
 ---
 
-# create
-
 ```
 Creates containers for a service.
 

compose/reference/down.md

@@ -1,16 +1,10 @@
 ---
-description: down
+description: docker-compose down
 keywords:
 - fig, composition, compose, docker, orchestration, cli,  down
-menu:
-  main:
-    identifier: down.compose
-    parent: smn_compose_cli
-title: down
+title: docker-compose down
 ---
 
-# down
-
 ```
 Usage: down [options]
 

compose/reference/envvars.md

@@ -1,16 +1,10 @@
 ---
-description: CLI Environment Variables
+description: Compose CLI environment variables
 keywords:
 - fig, composition, compose, docker, orchestration, cli,  reference
-menu:
-  main:
-    parent: smn_compose_cli
-    weight: -1
-title: CLI Environment Variables
+title: Compose CLI environment variables
 ---
 
-# CLI Environment Variables
-
 Several environment variables are available for you to configure the Docker Compose command-line behaviour.
 
 Variables starting with `DOCKER_` are the same as those used to configure the

compose/reference/events.md

@@ -2,15 +2,9 @@
 description: Receive real time events from containers.
 keywords:
 - fig, composition, compose, docker, orchestration, cli, events
-menu:
-  main:
-    identifier: events.compose
-    parent: smn_compose_cli
-title: events
+title: docker-compose events
 ---
 
-# events
-
 ```
 Usage: events [options] [SERVICE...]
 

compose/reference/exec.md

@@ -1,16 +1,10 @@
 ---
-description: exec
+description: docker-compose exec
 keywords:
 - fig, composition, compose, docker, orchestration, cli,  exec
-menu:
-  main:
-    identifier: exec.compose
-    parent: smn_compose_cli
-title: exec
+title: docker-compose exec
 ---
 
-# exec
-
 ```
 Usage: exec [options] SERVICE COMMAND [ARGS...]
 

compose/reference/help.md

@@ -1,16 +1,10 @@
 ---
-description: help
+description: docker-compose help
 keywords:
 - fig, composition, compose, docker, orchestration, cli,  help
-menu:
-  main:
-    identifier: help.compose
-    parent: smn_compose_cli
-title: help
+title: docker-compose help
 ---
 
-# help
-
 ```
 Usage: help COMMAND
 ```

compose/reference/index.md

@@ -2,16 +2,9 @@
 description: Compose CLI reference
 keywords:
 - fig, composition, compose, docker, orchestration, cli,  reference
-menu:
-  main:
-    identifier: smn_compose_cli
-    parent: workw_compose
-    weight: 80
-title: Command-line Reference
+title: Compose command-line reference
 ---
 
-## Compose command-line reference
-
 The following pages describe the usage information for the [docker-compose](overview.md) subcommands. You can also see this information by running `docker-compose [SUBCOMMAND] --help` from the command line.
 
 * [docker-compose](overview.md)

compose/reference/kill.md

@@ -2,15 +2,9 @@
 description: Forces running containers to stop.
 keywords:
 - fig, composition, compose, docker, orchestration, cli,  kill
-menu:
-  main:
-    identifier: kill.compose
-    parent: smn_compose_cli
-title: kill
+title: docker-compose kill
 ---
 
-# kill
-
 ```
 Usage: kill [options] [SERVICE...]
 

compose/reference/logs.md

@@ -2,15 +2,9 @@
 description: Displays log output from services.
 keywords:
 - fig, composition, compose, docker, orchestration, cli,  logs
-menu:
-  main:
-    identifier: logs.compose
-    parent: smn_compose_cli
-title: logs
+title: docker-compose logs
 ---
 
-# logs
-
 ```
 Usage: logs [options] [SERVICE...]
 

compose/reference/overview.md

@@ -4,15 +4,9 @@ aliases:
 description: Overview of docker-compose CLI
 keywords:
 - fig, composition, compose, docker, orchestration, cli,  docker-compose
-menu:
-  main:
-    parent: smn_compose_cli
-    weight: -2
 title: Overview of docker-compose CLI
 ---
 
-# Overview of docker-compose CLI
-
 This page provides the usage information for the `docker-compose` Command.
 You can also see this information by running `docker-compose --help` from the
 command line.

compose/reference/pause.md

@@ -2,15 +2,9 @@
 description: Pauses running containers for a service.
 keywords:
 - fig, composition, compose, docker, orchestration, cli, pause
-menu:
-  main:
-    identifier: pause.compose
-    parent: smn_compose_cli
-title: pause
+title: docker-compose pause
 ---
 
-# pause
-
 ```
 Usage: pause [SERVICE...]
 ```

compose/reference/port.md

@@ -2,15 +2,9 @@
 description: Prints the public port for a port binding.s
 keywords:
 - fig, composition, compose, docker, orchestration, cli,  port
-menu:
-  main:
-    identifier: port.compose
-    parent: smn_compose_cli
-title: port
+title: docker-compose port
 ---
 
-# port
-
 ```
 Usage: port [options] SERVICE PRIVATE_PORT
 

compose/reference/ps.md

@@ -2,15 +2,9 @@
 description: Lists containers.
 keywords:
 - fig, composition, compose, docker, orchestration, cli,  ps
-menu:
-  main:
-    identifier: ps.compose
-    parent: smn_compose_cli
-title: ps
+title: docker-compose ps
 ---
 
-# ps
-
 ```none
 Usage: ps [options] [SERVICE...]
 
@@ -22,8 +16,8 @@ Lists containers.
 
 ```bash
 $ docker-compose ps
-         Name                        Command                 State             Ports         
+         Name                        Command                 State             Ports
 --------------------------------------------------------------------------------------------
-mywordpress_db_1          docker-entrypoint.sh mysqld      Up           3306/tcp             
+mywordpress_db_1          docker-entrypoint.sh mysqld      Up           3306/tcp
 mywordpress_wordpress_1   /entrypoint.sh apache2-for ...   Restarting   0.0.0.0:8000->80/tcp
 ```

compose/reference/pull.md

@@ -2,15 +2,9 @@
 description: Pulls service images.
 keywords:
 - fig, composition, compose, docker, orchestration, cli,  pull
-menu:
-  main:
-    identifier: pull.compose
-    parent: smn_compose_cli
-title: pull
+title: docker-compose pull
 ---
 
-# pull
-
 ```
 Usage: pull [options] [SERVICE...]
 

compose/reference/push.md

@@ -2,15 +2,9 @@
 description: Pushes service images.
 keywords:
 - fig, composition, compose, docker, orchestration, cli,  push
-menu:
-  main:
-    identifier: push.compose
-    parent: smn_compose_cli
-title: push
+title: docker-compose push
 ---
 
-# push
-
 ```
 Usage: push [options] [SERVICE...]
 

compose/reference/restart.md

@@ -2,15 +2,9 @@
 description: Restarts Docker Compose services.
 keywords:
 - fig, composition, compose, docker, orchestration, cli,  restart
-menu:
-  main:
-    identifier: restart.compose
-    parent: smn_compose_cli
-title: restart
+title: docker-compose restart
 ---
 
-# restart
-
 ```
 Usage: restart [options] [SERVICE...]
 

compose/reference/rm.md

@@ -2,15 +2,9 @@
 description: Removes stopped service containers.
 keywords:
 - fig, composition, compose, docker, orchestration, cli,  rm
-menu:
-  main:
-    identifier: rm.compose
-    parent: smn_compose_cli
-title: rm
+title: docker-compose rm
 ---
 
-# rm
-
 ```
 Usage: rm [options] [SERVICE...]
 

compose/reference/run.md

@@ -2,15 +2,9 @@
 description: Runs a one-off command on a service.
 keywords:
 - fig, composition, compose, docker, orchestration, cli,  run
-menu:
-  main:
-    identifier: run.compose
-    parent: smn_compose_cli
-title: run
+title: docker-compose run
 ---
 
-# run
-
 ```
 Usage: run [options] [-e KEY=VAL...] SERVICE [COMMAND] [ARGS...]
 

compose/reference/scale.md

@@ -2,14 +2,9 @@
 description: Sets the number of containers to run for a service.
 keywords:
 - fig, composition, compose, docker, orchestration, cli,  scale
-menu:
-  main:
-    parent: smn_compose_cli
-title: scale
+title: docker-compose scale
 ---
 
-# scale
-
 ```
 Usage: scale [SERVICE=NUM...]
 ```

compose/reference/start.md

@@ -2,15 +2,9 @@
 description: Starts existing containers for a service.
 keywords:
 - fig, composition, compose, docker, orchestration, cli,  start
-menu:
-  main:
-    identifier: start.compose
-    parent: smn_compose_cli
-title: start
+title: docker-compose start
 ---
 
-# start
-
 ```
 Usage: start [SERVICE...]
 ```

compose/reference/stop.md

@@ -2,15 +2,9 @@
 description: 'Stops running containers without removing them. '
 keywords:
 - fig, composition, compose, docker, orchestration, cli, stop
-menu:
-  main:
-    identifier: stop.compose
-    parent: smn_compose_cli
-title: stop
+title: docker-compose stop
 ---
 
-# stop
-
 ```
 Usage: stop [options] [SERVICE...]
 

compose/reference/unpause.md

@@ -2,15 +2,9 @@
 description: Unpauses paused containers for a service.
 keywords:
 - fig, composition, compose, docker, orchestration, cli, unpause
-menu:
-  main:
-    identifier: unpause.compose
-    parent: smn_compose_cli
-title: unpause
+title: docker-compose unpause
 ---
 
-# unpause
-
 ```
 Usage: unpause [SERVICE...]
 ```

compose/reference/up.md

@@ -2,15 +2,9 @@
 description: Builds, (re)creates, starts, and attaches to containers for a service.
 keywords:
 - fig, composition, compose, docker, orchestration, cli,  up
-menu:
-  main:
-    identifier: up.compose
-    parent: smn_compose_cli
-title: up
+title: docker-compose up
 ---
 
-# up
-
 ```
 Usage: up [options] [SERVICE...]
 

compose/startup-order.md

@@ -1,15 +1,9 @@
 ---
 description: How to control service startup order in Docker Compose
 keywords: documentation, docs,  docker, compose, startup, order
-menu:
-  main:
-    parent: workw_compose
-    weight: 90
-title: Controlling startup order
+title: Controlling startup order in Compose
 ---
 
-# Controlling startup order in Compose
-
 You can control the order of service startup with the
 [depends_on](compose-file.md#depends-on) option. Compose always starts
 containers in dependency order, where dependencies are determined by
@@ -56,7 +50,7 @@ script:
 -   Alternatively, write your own wrapper script to perform a more application-specific health
     check. For example, you might want to wait until Postgres is definitely
     ready to accept commands:
-    
+
     wait-for-postgres.sh
 
         #!/bin/bash

compose/swarm.md

@@ -2,14 +2,9 @@
 description: How to use Compose and Swarm together to deploy apps to multi-host clusters
 keywords:
 - documentation, docs,  docker, compose, orchestration, containers, swarm
-menu:
-  main:
-    parent: workw_compose
-title: Using Compose with Swarm
+title: Use Compose with Swarm
 ---
 
-# Using Compose with Swarm
-
 Docker Compose and [Docker Swarm](/swarm/overview.md) aim to have full integration, meaning
 you can point a Compose app at a Swarm cluster and have it all just work as if
 you were using a single Docker host.

compose/wordpress.md

@@ -2,15 +2,9 @@
 description: Getting started with Compose and WordPress
 keywords:
 - documentation, docs,  docker, compose, orchestration, containers
-menu:
-  main:
-    parent: workw_compose
-    weight: 6
-title: 'Quickstart: Compose and WordPress'
+title: "Quickstart: Compose and WordPress"
 ---
 
-# Quickstart: Docker Compose and WordPress
-
 You can use Docker Compose to easily run WordPress in an isolated environment built
 with Docker containers. This quick-start guide demonstrates how to use Compose to set up and run WordPress. Before starting, you'll need to have
 [Compose installed](install.md).

cs-engine/index.md

@@ -4,15 +4,9 @@ aliases:
 description: Learn more about the Commercially Supported Docker Engine.
 keywords:
 - docker, engine, documentation
-menu:
-  main:
-    identifier: menu_csengine
-    weight: -65
-title: CS Docker Engine
+title: Commercially Supported Docker Engine
 ---
 
-# Docker CS Engine
-
 This section includes the following topics:
 
 * [Install CS Docker Engine](install.md)

cs-engine/install.md

@@ -6,16 +6,9 @@ aliases:
 description: Learn how to install the commercially supported version of Docker Engine.
 keywords:
 - docker, engine, dtr, install
-menu:
-  main:
-    identifier: csengine_install
-    parent: menu_csengine
-    weight: 0
-title: Install CS Docker Engine
+title: Install Commercially Supported Docker Engine
 ---
 
-# Install CS Docker Engine
-
 Follow these instructions to install CS Docker Engine, the commercially
 supported version of Docker Engine.
 

cs-engine/release-notes/index.md

@@ -4,15 +4,8 @@ aliases:
 description: The release notes for CS Docker Engine.
 keywords:
 - docker, engine, release notes
-menu:
-  main:
-    identifier: menu_csengine_release_notes
-    parent: menu_csengine
-    weight: 100
-title: Release notes
+title: Commercially Supported Docker Engine release notes
 ---
 
-# Docker CS Engine release notes
-
 * [Release notes](release-notes.md)
 * [Prior release notes](prior-release-notes.md)

cs-engine/release-notes/prior-release-notes.md

@@ -4,18 +4,10 @@ aliases:
 - /docker-trusted-registry/cs-engine/release-notes/prior-release-notes/
 description: Archived release notes for commercially supported Docker Engine
 keywords:
-- docker, documentation, about, technology, understanding, enterprise, hub, registry,release,
-  commercially supported Docker Engine
-menu:
-  main:
-    identifier: csengine_prior_release_notes
-    parent: menu_csengine_release_notes
-    weight: 10
-title: Prior CS Engine release notes
+- docker, documentation, about, technology, understanding, enterprise, hub, registry, release, commercially supported Docker Engine
+title: Release notes archive for Commercially Supported Docker Engine.
 ---
 
-# CS Engine release notes archive
-
 This document contains the previous versions of the commercially supported
 Docker Engine release notes. It includes issues, fixes, and new features.
 

cs-engine/release-notes/release-notes.md

@@ -4,18 +4,10 @@ aliases:
 - /docker-trusted-registry/cs-engine/release-notes/release-notes/
 description: Commercially supported Docker Engine release notes
 keywords:
-- docker, documentation, about, technology, understanding, enterprise, hub, registry,
-  Commercially Supported Docker Engine, release notes
-menu:
-  main:
-    identifier: csengine_release_notes
-    parent: menu_csengine_release_notes
-    weight: 0
-title: CS Engine release notes
+- docker, documentation, about, technology, understanding, enterprise, hub, registry, Commercially Supported Docker Engine, release notes
+title: Commercially Supported Engine release notes
 ---
 
-# Commercially supported Engine release notes
-
 This document describes the latest changes, additions, known issues, and fixes
 for the commercially supported Docker Engine (CS Engine).
 

cs-engine/upgrade.md

@@ -4,16 +4,9 @@ aliases:
 description: Learn how to install the commercially supported version of Docker Engine.
 keywords:
 - docker, engine, dtr, upgrade
-menu:
-  main:
-    identifier: csengine_upgrade
-    parent: menu_csengine
-    weight: 10
-title: Upgrade
+title: Upgrade Commercially Supported Docker Engine
 ---
 
-# Upgrade CS Docker Engine
-
 This article explains how to upgrade your CS Docker Engine.
 
 The upgrade process depends on the version that is currently installed and the

docker-cloud/apps/api-roles.md

@@ -4,14 +4,9 @@ aliases:
 description: API Roles
 keywords:
 - API, Services, roles
-menu:
-  main:
-    parent: apps
-title: Service API Roles
+title: Service API roles
 ---
 
-# Service API Roles
-
 You can configure a service so that it can access the Docker Cloud API. When you
 grant API access to a service, its containers receive a token through an
 environment variable, which is used to query the Docker Cloud API.

docker-cloud/apps/auto-destroy.md

@@ -4,14 +4,9 @@ aliases:
 description: Autodestroy
 keywords:
 - Autodestroy, service, terminate, container
-menu:
-  main:
-    parent: apps
-title: Automatic container destroy
+title: Destroy containers automatically
 ---
 
-# Autodestroy
-
 When enabled on a service, **Autodestroy**  automatically terminates containers
 when they stop. **This destroys all data in the container on stop.** This is
 useful for one-time actions that store their results in an external system.

docker-cloud/apps/auto-redeploy.md

@@ -4,14 +4,9 @@ aliases:
 description: Autoredeploy
 keywords:
 - Autoredeploy, image, store, service
-menu:
-  main:
-    parent: apps
-title: Automatic service redeploy
+title: Redeploy services automatically
 ---
 
-# Autoredeploy
-
 Docker Cloud's **Autoredeploy** feature allows a service that uses an image
 stored in Docker Hub to automatically redeploy whenever a new image is pushed or
 built.

docker-cloud/apps/autorestart.md

@@ -4,14 +4,9 @@ aliases:
 description: Automatically restart a container in Docker Cloud
 keywords:
 - container, restart, automated
-menu:
-  main:
-    parent: apps
-title: Automatic container restart
+title: Restart a container automatically
 ---
 
-# Automatically restart a container
-
 **Autorestart** is a service-level setting that can automatically start your
 containers if they stop or crash. You can use this setting as an automatic crash
 recovery mechanism.

docker-cloud/apps/deploy-tags.md

@@ -4,14 +4,9 @@ aliases:
 description: Deployment tags
 keywords:
 - Deployment, tags, services
-menu:
-  main:
-    parent: apps
 title: Deployment tags
 ---
 
-# Deployment tags
-
 You can use **Deployment tags** to make sure certain services are deployed only
 to specific nodes. Tagged services only deploy to nodes that match **all** of
 the tags on that service. Docker Cloud shows an error if no nodes match all of

docker-cloud/apps/deploy-to-cloud-btn.md

@@ -5,14 +5,9 @@ aliases:
 description: Deploy to Docker Cloud
 keywords:
 - deploy, docker, cloud
-menu:
-  main:
-    parent: apps
-title: Add a Deploy to Docker Cloud button
+title: Add a "Deploy to Docker Cloud" button
 ---
 
-# Add a Deploy to Docker Cloud Button
-
 The **Deploy to Docker Cloud** button allows developers to deploy stacks with one click in Docker Cloud. The button is intended to be added to `README.md` files in public GitHub repositories, although it can be used anywhere else.
 
 This is an example button to deploy our <a href="https://github.com/docker/dockercloud-quickstart-python" target="_blank">python quickstart</a>:

docker-cloud/apps/index.md

@@ -2,15 +2,9 @@
 description: Manage your Docker Cloud Applications
 keywords:
 - applications, reference, Cloud
-menu:
-  main:
-    parent: apps
-    weight: -99
 title: Applications in Docker Cloud
 ---
 
-# Applications in Docker Cloud
-
 Applications in Docker Cloud are usually several Services linked together using
 the specifications from a [Stackfile](stacks.md) or a Compose file. You can also
 create individual services using the Docker Cloud Services wizard, and you can

docker-cloud/apps/load-balance-hello-world.md

@@ -5,14 +5,9 @@ aliases:
 description: Create a proxy or load balancer
 keywords:
 - proxy, load, balancer
-menu:
-  main:
-    parent: apps
 title: Create a proxy or load balancer
 ---
 
-# Create a proxy or load balancer
-
 When you deploy a web service to multiple containers you might want to load
 balance between the containers using a proxy or load balancer.
 

docker-cloud/apps/ports.md

@@ -4,15 +4,12 @@ aliases:
 description: Publish and expose service or container ports
 keywords:
 - publish, expose, ports, containers, services
-menu:
-  main:
-    parent: apps
 title: Publish and expose service or container ports
 ---
 
-# Publish and expose service or container ports
-
-In Docker Cloud you can **publish** or **expose** ports in services and containers, just like you can in Docker Engine (as documented [here](/reference/run/#expose-incoming-ports) ).
+In Docker Cloud you can **publish** or **expose** ports in services and
+containers, just like you can in Docker Engine (as documented
+[here](/reference/run/#expose-incoming-ports) ).
 
 * **Exposed ports** are ports that a container or service is using either to
 provide a service, or listen on. By default, exposed ports in Docker Cloud are

docker-cloud/apps/service-links.md

@@ -4,14 +4,9 @@ aliases:
 description: Service discovery
 keywords:
 - service, discover, links
-menu:
-  main:
-    parent: apps
 title: Service discovery and links
 ---
 
-# Service discovery and links
-
 Docker Cloud creates a per-user overlay network which connects all containers across all of the user's hosts. This network connects all of your containers on the `10.7.0.0/16` subnet, and gives every container a local IP. This IP persists on each container even if the container is redeployed and ends up on a different host. Every container can reach any other container on any port within the subnet.
 
 Docker Cloud gives your containers two ways find other services:

docker-cloud/apps/service-redeploy.md

@@ -4,14 +4,9 @@ aliases:
 description: Redeploy running services
 keywords:
 - redeploy, running, services
-menu:
-  main:
-    parent: apps
-title: Redeploy running services
+title: Redeploy a running service
 ---
 
-# Redeploy a running service
-
 You can **redeploy** services in Docker Cloud while they are running to
 regenerate a service's containers. You might do this when a new version of the
 image is pushed to the registry, or in order to apply changes that you made to

docker-cloud/apps/service-scaling.md

@@ -4,14 +4,9 @@ aliases:
 description: Scale your service, spawn new containers
 keywords:
 - spawn, container, service, deploy
-menu:
-  main:
-    parent: apps
 title: Scale your service
 ---
 
-# Scale your service
-
 Docker Cloud makes it easy to spawn new containers of your service to handle
 additional load. Two modes are available to allow you to scale services with
 different configuration requirements.

docker-cloud/apps/stack-yaml-reference.md

@@ -4,14 +4,9 @@ aliases:
 description: Stack YAML reference
 keywords:
 - YAML, stack, reference
-menu:
-  main:
-    parent: apps
-title: Stack YAML reference
+title: Stack file YAML reference
 ---
 
-# Stack YAML reference
-
 A stack is a collection of services that make up an application in a specific environment. Learn more about stacks [here](stacks.md). A **stack file** is a file in YAML format that defines one or more services, similar to a `docker-compose.yml` file but with a few extensions. The default name for this file is `docker-cloud.yml`.
 
 ## Stack file example

docker-cloud/apps/stacks.md

@@ -4,14 +4,9 @@ aliases:
 description: Manage service stacks
 keywords:
 - service, stack, yaml
-menu:
-  main:
-    parent: apps
 title: Manage service stacks
 ---
 
-# Manage service stacks
-
 A **stack** is a collection of services that make up an application in a specific environment. A **stack file** is a file in YAML format, similar to a `docker-compose.yml` file, that defines one or more services. The YAML reference is documented [here](stack-yaml-reference.md).
 
 Stacks are a convenient way to automatically deploy multiple services that are linked to each other, without needing to define each one separately.

docker-cloud/apps/triggers.md

@@ -4,14 +4,9 @@ aliases:
 description: Use triggers
 keywords:
 - API, triggers, endpoints
-menu:
-  main:
-    parent: apps
 title: Use triggers
 ---
 
-# Use triggers
-
 **Triggers** are API endpoints that redeploy or scale a specific service
 whenever a `POST` HTTP request is sent to them. You can create one or more
 triggers per service.

docker-cloud/apps/volumes.md

@@ -5,14 +5,9 @@ aliases:
 description: Work with data volumes
 keywords:
 - data, volumes, create, reuse
-menu:
-  main:
-    parent: apps
 title: Work with data volumes
 ---
 
-# Work with data volumes
-
 In Docker Cloud, you can define one or more data volumes for a service.
 **Volumes** are directories that are stored outside of the container's
 filesystem and which hold reusable and shareable data that can persist even when

docker-cloud/builds/advanced.md

@@ -2,15 +2,9 @@
 description: Automated builds
 keywords:
 - automated, build, images
-menu:
-  main:
-    parent: builds
-    weight: -40
 title: Advanced options for Autobuild and Autotest
 ---
 
-# Advanced options for Autobuild and Autotest
-
 The following options allow you to customize your automated build and automated test processes.
 
 ## Environment variables for building and testing

docker-cloud/builds/automated-build.md

@@ -4,15 +4,9 @@ aliases:
 description: Automated builds
 keywords:
 - automated, build, images
-menu:
-  main:
-    parent: builds
-    weight: -50
 title: Automated builds
 ---
 
-# Automated builds
-
 > **Note**: Docker Cloud's Build functionality is in BETA.
 
 Docker Cloud can automatically build images from source code in an external

docker-cloud/builds/automated-testing.md

@@ -4,15 +4,9 @@ aliases:
 description: Automated tests
 keywords:
 - Automated, testing, repository
-menu:
-  main:
-    parent: builds
-    weight: -50
 title: Automated repository tests
 ---
 
-# Automated repository tests
-
 Docker Cloud can automatically test changes pushed to your source code
 repositories using containers. You can enable `Autotest` on [any Docker Cloud repository](repos.md) to run tests at each push to the source code repository,
 similar to a continuous integration testing service.

docker-cloud/builds/image-scan.md

@@ -1,17 +1,10 @@
 ---
-description: 'Docker Security Scanning: automatic image scanning'
+description: "Docker Security Scanning: automatic image scanning"
 keywords:
-- Docker, docker, scan, scanning, security, registry, plans, Docker Cloud, docs, documentation,
-  trusted, builds, trusted builds, automated builds
-menu:
-  main:
-    parent: builds
-    weight: -55
+- Docker, docker, scan, scanning, security, registry, plans, Docker Cloud, docs, documentation, trusted, builds, trusted builds, automated builds
 title: Docker Security Scanning
 ---
 
-# Docker Security Scanning
-
 Docker Cloud and Docker Hub can scan images in private repositories to verify
 that they are free from known security vulnerabilities or exposures, and report
 the results of the scan for each image tag.

docker-cloud/builds/index.md

@@ -2,16 +2,10 @@
 description: Manage Builds and Images in Docker Cloud
 keywords:
 - builds, images, Cloud
-menu:
-  main:
-    parent: builds
-    weight: -80
 notoc: true
-title: Builds and Images Overview
+title: Builds and images overview
 ---
 
-# Builds and Images Overview
-
 Docker Cloud provides a hosted registry service where you can create
 repositories to store your Docker images. You can choose to push images to the
 repositories, or link to your source code and build them directly in Docker

docker-cloud/builds/link-source.md

@@ -3,15 +3,9 @@ aliases: /docker-cloud/tutorials/link-source/
 description: Link to your source code repository
 keywords:
 - sourcecode, github, bitbucket, Cloud
-menu:
-  main:
-    parent: builds
-    weight: -60
-title: Link to a source code repository
+title: Link Docker Cloud to a source code provider
 ---
 
-# Link Docker Cloud to a source code provider
-
 To automate building and testing of your images, you link to your hosted source
 code service to Docker Cloud so that it can access your source code
 repositories. You can configure this link for user accounts or

docker-cloud/builds/push-images.md

@@ -5,15 +5,9 @@ aliases:
 description: Push images to Docker Cloud
 keywords:
 - images, private, registry
-menu:
-  main:
-    parent: builds
-    weight: -60
 title: Push images to Docker Cloud
 ---
 
-# Push images to Docker Cloud
-
 Docker Cloud uses Docker Hub as its native registry for storing both public and
 private repositories. Once you push your images to Docker Hub, they will be
 available in Docker Cloud.

docker-cloud/builds/repos.md

@@ -2,15 +2,9 @@
 description: Create and edit Docker Cloud repositories
 keywords:
 - Docker Cloud repositories, automated, build, images
-menu:
-  main:
-    parent: builds
-    weight: -70
 title: Docker Cloud repositories
 ---
 
-# Docker Cloud repositories
-
 Repositories in Docker Cloud store your Docker images. You can create
 repositories and manually [push images](push-images.md) using `docker push`, or
 you can link to a source code provider and use [automated builds](automated-build.md) to build the images for you. These repositories

docker-cloud/docker-errors-faq.md

@@ -4,15 +4,9 @@ aliases:
 description: Known Docker Engine issues in Docker Cloud
 keywords:
 - Engine, issues, troubleshoot
-menu:
-  main:
-    parent: docker-cloud
-    weight: 50
-title: Known Issues in Docker Cloud
+title: Known issues in Docker Cloud
 ---
 
-# Known Docker Engine issues in Docker Cloud
-
 This is a list of known issues with current versions of Docker Engine along with our recommended workaround. You might encounter these errors in Docker Cloud.
 
 ---

docker-cloud/dockerid.md

@@ -2,15 +2,9 @@
 description: Using your DockerID to log in to Docker Cloud
 keywords:
 - one, two, three
-menu:
-  main:
-    parent: docker-cloud
-    weight: -99
-title: Docker ID and Settings
+title: Docker ID and Docker Cloud settings
 ---
 
-# Your Docker ID and Docker Cloud account
-
 Docker Cloud uses your Docker ID for access and access control, and this allows
 you to link your Hub and Cloud accounts.
 

docker-cloud/getting-started/connect-infra.md

@@ -1,21 +1,12 @@
 ---
 aliases:
 - /docker-cloud/getting-started/use-hosted/
-description: How to link Docker Cloud to a hosted cloud services provider or your
-  own hosts
+description: How to link Docker Cloud to a hosted cloud services provider or your own hosts
 keywords:
 - node, create, understand
-menu:
-  main:
-    aliases:
-    - /docker-cloud/getting-started/use-hosted/
-    parent: getting-started
-    weight: -90
-title: Link to your Infrastructure
+title: Link to your infrastructure
 ---
 
-# Link to your Infrastructure
-
 To deploy Docker Cloud nodes, you first need to grant Docker Cloud access to your infrastructure.
 
 This could mean granting access to a cloud services provider such as AWS or Azure, or installing the Docker Cloud Agent on your own hosts. Once this is done, you can provision nodes directly from within Docker Cloud using the Web UI, CLI or API.

docker-cloud/getting-started/deploy-app/10_provision_a_data_backend_for_your_service.md

@@ -5,15 +5,9 @@ aliases:
 description: Provision a data backend for the service
 keywords:
 - provision, Python, service
-menu:
-  main:
-    parent: deploy-app
-    weight: -9
-title: Provision a data backend for the service
+title: Provision a data backend for your service
 ---
 
-# Provision a data backend for a Python service
-
 Docker Cloud offers a large number of data stores in the *Jumpstart* library, including Redis, MongoDB, PostgreSQL, and MySQL.
 
 You may have noticed that your app has a visit counter that's been disabled up

docker-cloud/getting-started/deploy-app/11_service_stacks.md

@@ -4,15 +4,9 @@ aliases:
 description: Stackfiles for your service
 keywords:
 - Python, service, stack
-menu:
-  main:
-    parent: deploy-app
-    weight: -8
 title: Stackfiles for your service
 ---
 
-# Stackfiles for your service
-
 A stack is a logical grouping of related services that are usually deployed together and require each other to work as intended. If you are familiar with *fig* or *Docker Compose* then you should feel right at home with **stacks**. You can learn more about stacks [here](../../apps/stacks.md).
 
 Stack files are YAML files, and you can learn more about the available syntax [here](../../apps/stack-yaml-reference.md). You can also interact with stacks using the [stack commands in our API](/apidocs/docker-cloud.md#stacks).

docker-cloud/getting-started/deploy-app/12_data_management_with_volumes.md

@@ -4,15 +4,9 @@ aliases:
 description: Data management with Volumes
 keywords:
 - Python, data, management
-menu:
-  main:
-    parent: deploy-app
-    weight: -5
-title: Data management with Volumes
+title: Data management with volumes
 ---
 
-# Data management with Volumes
-
 In the previous step, we set up Redis but didn't provide it a way to store the
 data it's caching. This means that if you redeployed the redis service, or if
 the container crashed, the data would be lost. To save the data so it persists

docker-cloud/getting-started/deploy-app/1_introduction.md

@@ -5,15 +5,9 @@ aliases:
 description: Deploy an app to Docker Cloud
 keywords:
 - deploy, Python, application
-menu:
-  main:
-    parent: deploy-app
-    weight: -90
-title: Introduction to Deploying an app in Docker Cloud
+title: Introduction to deploying an app in Docker Cloud
 ---
 
-# Introduction and tutorial prerequisites
-
 In this tutorial you will bring an application to Docker Cloud using either Go or
 Python. This tutorial is intended for more advanced beginners who have some
 experience with web applications, and who want to learn more about

docker-cloud/getting-started/deploy-app/2_set_up.md

@@ -5,15 +5,9 @@ aliases:
 description: Set up the application
 keywords:
 - Python, application, setup
-menu:
-  main:
-    parent: deploy-app
-    weight: -80
 title: Set up your environment
 ---
 
-# Set up your environment
-
 In this step you install the Docker Cloud CLI so interact with the service using your command shell. This tutorial uses CLI commands to complete actions.
 
 ## Install the Docker Cloud CLI

docker-cloud/getting-started/deploy-app/3_prepare_the_app.md

@@ -5,15 +5,9 @@ aliases:
 description: Prepare the application
 keywords:
 - Python, prepare, application
-menu:
-  main:
-    parent: deploy-app
-    weight: -70
 title: Prepare the application
 ---
 
-# Prepare the application
-
 In this step, you will prepare a simple application that can be deployed.
 Run the following command to clone the sample application. You can use
 either the Python or the Go version of this application, but you don't need to

docker-cloud/getting-started/deploy-app/4_push_to_cloud_registry.md

@@ -5,15 +5,9 @@ aliases:
 description: Push the Docker image to Docker Cloud's Registry
 keywords:
 - image, Docker, cloud
-menu:
-  main:
-    parent: deploy-app
-    weight: -60
-title: Push the image to Docker Cloud's Registry
+title: Push the image to Docker Cloud's registry
 ---
 
-# Push the image to Docker Cloud's Registry
-
 *Skip this step if you don't have Docker Engine installed locally.*
 
 In this step you will take the image that you built in the previous step, and push it to Docker Cloud.

docker-cloud/getting-started/deploy-app/5_deploy_the_app_as_a_service.md

@@ -5,15 +5,9 @@ aliases:
 description: Deploy the app as a Docker Cloud service
 keywords:
 - Python, deploy, Cloud
-menu:
-  main:
-    parent: deploy-app
-    weight: -50
 title: Deploy the app as a Docker Cloud service
 ---
 
-# Deploy the app as a Docker Cloud service
-
 In this step you will deploy the app as a Docker Cloud Service. Remember that a service is a group of containers of the same **image:tag**.
 
 What you'll do in this step is slightly different if you have Docker Engine installed locally or not.

docker-cloud/getting-started/deploy-app/6_define_environment_variables.md

@@ -5,15 +5,9 @@ aliases:
 description: Define environment variables
 keywords:
 - Python, service, environment, service
-menu:
-  main:
-    parent: deploy-app
-    weight: -40
 title: Define environment variables
 ---
 
-# Define environment variables
-
 Docker lets you store data such as configuration settings, encryption keys, and external resource addresses in environment variables. Docker Cloud makes it easy to define, share, and update the environment variables for your services.
 
 At runtime, environment variables are exposed to the application inside the container. Let's look inside the app you just deployed.

docker-cloud/getting-started/deploy-app/7_scale_the_service.md

@@ -5,15 +5,9 @@ aliases:
 description: Scale the service
 keywords:
 - scale, Python, service
-menu:
-  main:
-    parent: deploy-app
-    weight: -30
 title: Scale the service
 ---
 
-# Scale the service
-
 Right now, your service is running on a single container. That's great for now.
 
 You can check how many containers are running using the `docker-cloud container ps` command.

docker-cloud/getting-started/deploy-app/8_view_logs.md

@@ -5,15 +5,9 @@ aliases:
 description: View service logs
 keywords:
 - View, logs, Python
-menu:
-  main:
-    parent: deploy-app
-    weight: -20
 title: View service logs
 ---
 
-# View service logs
-
 Docker Cloud grants you access to the logs your application writes to `stdout`.
 An internal service multiplexes all the logs from all the containers of a
 service into a single stream. To see a service's logs run the `docker-cloud

docker-cloud/getting-started/deploy-app/9_load-balance_the_service.md

@@ -5,15 +5,9 @@ aliases:
 description: Load-balance the service
 keywords:
 - load, balance, Python
-menu:
-  main:
-    parent: deploy-app
-    weight: -10
 title: Load-balance the service
 ---
 
-# Load-balance a Python service
-
 To load-balance a your application, you need to deploy a load-balancing service.
 This service distributes incoming requests to all of the available containers in
 the application.

docker-cloud/getting-started/deploy-app/index.md

@@ -5,16 +5,9 @@ aliases:
 description: Go or Python and Docker Cloud
 keywords:
 - Python, Go, Docker, Cloud, application
-menu:
-  main:
-    identifier: deploy-app
-    parent: getting-started
-    weight: 50
 title: Deploy an application
 ---
 
-# Deploy an application
-
 * [Introduction to Deploying an app to Docker Cloud](1_introduction.md)
 * [Set up your environment](2_set_up.md)
 * [Prepare the application](3_prepare_the_app.md)

docker-cloud/getting-started/index.md

@@ -3,16 +3,9 @@ description: 'Getting Started with Docker Cloud: Setting up a node using a hoste
   cloud provider or your own nodes, deploying a service and clustering.'
 keywords:
 - one, two, three
-menu:
-  main:
-    identifier: getting-started
-    parent: docker-cloud
-    weight: -97
-title: Getting Started
+title: Getting started with Docker Cloud
 ---
 
-# Getting Started with Docker Cloud
-
 If you're completely new to Docker Cloud, start here!
 
 * [Introducing Docker Cloud](intro_cloud.md) Start here! Then, you can either:

docker-cloud/getting-started/intro_cloud.md

@@ -4,15 +4,9 @@ aliases:
 description: Introducing Docker Cloud concepts and terminology
 keywords:
 - node, create, understand
-menu:
-  main:
-    parent: getting-started
-    weight: -100
 title: Introducing Docker Cloud
 ---
 
-# Introducing Docker Cloud
-
 This page introduces core Docker Cloud concepts and features so you can easily follow along with the tutorial.
 
 The tutorial goes through the following steps:

docker-cloud/getting-started/your_first_node.md

@@ -5,15 +5,9 @@ aliases:
 description: Deploy your first node on Docker Cloud
 keywords:
 - node, create, understand
-menu:
-  main:
-    parent: getting-started
-    weight: -50
 title: Deploy your first node
 ---
 
-# Deploy Your First Node
-
 In this step you'll create your first node (inside a node cluster) on Docker Cloud.
 
 After you link your Docker Cloud account with your hosts (either your own hosts or one or more cloud providers), the next step is to launch your first node.

docker-cloud/getting-started/your_first_service.md

@@ -5,15 +5,9 @@ aliases:
 description: Deploy your first service on Docker Cloud
 keywords:
 - service, Cloud, three
-menu:
-  main:
-    parent: getting-started
-    weight: -40
-title: Deploy your first service
+title: Create your first service
 ---
 
-# Your first service
-
 This page describes how to create a service on Docker Cloud.
 
 ## What is a service?

docker-cloud/index.md

@@ -2,15 +2,10 @@
 description: Docker Cloud
 keywords:
 - Docker, cloud
-menu:
-  main:
-    identifier: docker-cloud
 notoc: true
-title: Docker Cloud
+title: Welcome to the Docker Cloud docs!
 ---
 
-# Welcome to the Docker Cloud Docs!
-
 <center>
 <img src="images/Docker-Cloud-Blue.png">
 </center>

docker-cloud/infrastructure/byoh.md

@@ -6,14 +6,9 @@ aliases:
 description: Use the Docker Cloud Agent
 keywords:
 - agent, Cloud, install
-menu:
-  main:
-    parent: infrastructure
 title: Use the Docker Cloud Agent
 ---
 
-# Use the Docker Cloud Agent
-
 Docker Cloud allows you to use any Linux host ("bring your own host") as a node which you can then use to deploy containers. To do this, you install the **Docker Cloud Agent** on your Linux host so that Docker Cloud can remotely manage it.
 
 The **Docker Cloud Agent** installs its own Docker binary, and automatically removes any prior installation of the Docker Engine packages. See the [Known Limitations](byoh.md#known-limitations) section for more information.