fix type of keywords entry in frontmatter (in /docker-cloud/ dir)

keywords should be a string, not an array containing one string Signed-off-by: Gaetan de Villele <[email protected]>
plus500s · Nov 8, 2016 · bcec1dd · bcec1dd
1 parent 5c815e0
commit bcec1dd
Show file tree

Hide file tree

Showing 62 changed files with 175 additions and 237 deletions.
diff --git a/docker-cloud/apps/api-roles.md b/docker-cloud/apps/api-roles.md
@@ -1,9 +1,8 @@
 ---
+description: API Roles
+keywords: API, Services, roles
 redirect_from:
 - /docker-cloud/feature-reference/api-roles/
-description: API Roles
-keywords:
-- API, Services, roles
 title: Service API roles
 ---
 
@@ -32,4 +31,4 @@ $ curl -H "Authorization: $DOCKERCLOUD_AUTH" -H "Accept: application/json" $WEB_
 For example, you can use information retrieved using the API to read the linked
 endpoints, and use them to reconfigure a proxy container.
 
-See the [API documentation](/apidocs/docker-cloud.md) for more information on the different API operations available.
+See the [API documentation](/apidocs/docker-cloud.md) for more information on the different API operations available.
diff --git a/docker-cloud/apps/auto-destroy.md b/docker-cloud/apps/auto-destroy.md
@@ -1,9 +1,8 @@
 ---
+description: Autodestroy
+keywords: Autodestroy, service, terminate, container
 redirect_from:
 - /docker-cloud/feature-reference/auto-destroy/
-description: Autodestroy
-keywords:
-- Autodestroy, service, terminate, container
 title: Destroy containers automatically
 ---
 
@@ -75,4 +74,4 @@ PATCH /api/app/v1/service/(uuid)/ HTTP/1.1
 #### Enabling autodestroy using the CLI
 ```
 $ docker-cloud service set --autodestroy ALWAYS (name or uuid)
-```
+```
diff --git a/docker-cloud/apps/auto-redeploy.md b/docker-cloud/apps/auto-redeploy.md
@@ -1,9 +1,8 @@
 ---
+description: Autoredeploy
+keywords: Autoredeploy, image, store, service
 redirect_from:
 - /docker-cloud/feature-reference/auto-redeploy/
-description: Autoredeploy
-keywords:
-- Autoredeploy, image, store, service
 title: Redeploy services automatically
 ---
 
@@ -76,4 +75,4 @@ PATCH /api/app/v1/service/(uuid)/ HTTP/1.1
 {
 	"autoredeploy": true
 }
-```
+```
diff --git a/docker-cloud/apps/autorestart.md b/docker-cloud/apps/autorestart.md
@@ -1,9 +1,8 @@
 ---
+description: Automatically restart a container in Docker Cloud
+keywords: container, restart, automated
 redirect_from:
 - /docker-cloud/feature-reference/autorestart/
-description: Automatically restart a container in Docker Cloud
-keywords:
-- container, restart, automated
 title: Restart a container automatically
 ---
 
@@ -86,4 +85,4 @@ PATCH /api/app/v1/service/(uuid)/ HTTP/1.1
 $ docker-cloud service set --autorestart ALWAYS (name or uuid)
 ```
 
-See the [API documentation](/apidocs/docker-cloud.md) for more information.
+See the [API documentation](/apidocs/docker-cloud.md) for more information.
diff --git a/docker-cloud/apps/deploy-tags.md b/docker-cloud/apps/deploy-tags.md
@@ -1,9 +1,8 @@
 ---
+description: Deployment tags
+keywords: Deployment, tags, services
 redirect_from:
 - /docker-cloud/feature-reference/deploy-tags/
-description: Deployment tags
-keywords:
-- Deployment, tags, services
 title: Deployment tags
 ---
 
@@ -116,4 +115,4 @@ be deployed to the nodes that match the new tags.
 
 ## Using deployment tags in the API and CLI
 
-See the [tags API and CLI documentation](/apidocs/docker-cloud.md#tags) for more information on how to use tags with our API and CLI.
+See the [tags API and CLI documentation](/apidocs/docker-cloud.md#tags) for more information on how to use tags with our API and CLI.
diff --git a/docker-cloud/apps/deploy-to-cloud-btn.md b/docker-cloud/apps/deploy-to-cloud-btn.md
@@ -1,10 +1,9 @@
 ---
+description: Deploy to Docker Cloud
+keywords: deploy, docker, cloud
 redirect_from:
 - /docker-cloud/feature-reference/deploy-to-cloud/
 - /docker-cloud/tutorials/deploy-to-cloud/
-description: Deploy to Docker Cloud
-keywords:
-- deploy, docker, cloud
 title: Add a "Deploy to Docker Cloud" button
 ---
 
@@ -61,4 +60,4 @@ where `<repo_url>` is the path to your GitHub repository. For example:
 
 You can use your own image for the link (or no image). Our **Deploy to Docker Cloud** image is available at the following URL:
 
-* `https://files.cloud.docker.com/images/deploy-to-dockercloud.svg`
+* `https://files.cloud.docker.com/images/deploy-to-dockercloud.svg`
diff --git a/docker-cloud/apps/index.md b/docker-cloud/apps/index.md
@@ -1,7 +1,6 @@
 ---
 description: Manage your Docker Cloud Applications
-keywords:
-- applications, reference, Cloud
+keywords: applications, reference, Cloud
 title: Applications in Docker Cloud
 ---
 
@@ -33,4 +32,4 @@ Use the following features to automate specific actions on your Docker Cloud app
 * [Automatic container destroy](auto-destroy.md)
 * [Automatic container restart](autorestart.md)
 * [Autoredeploy](auto-redeploy.md)
-* [Use triggers](triggers.md)
+* [Use triggers](triggers.md)
diff --git a/docker-cloud/apps/load-balance-hello-world.md b/docker-cloud/apps/load-balance-hello-world.md
@@ -1,10 +1,9 @@
 ---
+description: Create a proxy or load balancer
+keywords: proxy, load, balancer
 redirect_from:
 - /docker-cloud/getting-started/intermediate/load-balance-hello-world/
 - /docker-cloud/tutorials/load-balance-hello-world/
-description: Create a proxy or load balancer
-keywords:
-- proxy, load, balancer
 title: Create a proxy or load balancer
 ---
 
@@ -197,4 +196,4 @@ links](service-links.md).
 
 You can try this by pointing your web browser to
 *servicename.username.svc.dockerapp.io* or  using *dig* or *nslookup* to see how
-the service endpoint resolves.
+the service endpoint resolves.
diff --git a/docker-cloud/apps/ports.md b/docker-cloud/apps/ports.md
@@ -1,9 +1,8 @@
 ---
+description: Publish and expose service or container ports
+keywords: publish, expose, ports, containers, services
 redirect_from:
 - /docker-cloud/feature-reference/ports/
-description: Publish and expose service or container ports
-keywords:
-- publish, expose, ports, containers, services
 title: Publish and expose service or container ports
 ---
 
@@ -122,4 +121,4 @@ not dynamic) is assigned a DNS endpoint in the format
 running, in a [round-robin
 fashion](https://en.wikipedia.org/wiki/Round-robin_DNS).
 
-You can see a list of service endpoints on the stack and service detail views, under the **Endpoints** tab.
+You can see a list of service endpoints on the stack and service detail views, under the **Endpoints** tab.
diff --git a/docker-cloud/apps/service-links.md b/docker-cloud/apps/service-links.md
@@ -1,9 +1,8 @@
 ---
+description: Service discovery
+keywords: service, discover, links
 redirect_from:
 - /docker-cloud/feature-reference/service-links/
-description: Service discovery
-keywords:
-- service, discover, links
 title: Service discovery and links
 ---
 
@@ -162,4 +161,4 @@ Where:
 
 These environment variables are also copied to linked containers with the `NAME_ENV_` prefix.
 
-If you provide API access to your service, you can use the generated token (stored in `DOCKERCLOUD_AUTH`) to access these API URLs to gather information or automate operations, such as scaling.
+If you provide API access to your service, you can use the generated token (stored in `DOCKERCLOUD_AUTH`) to access these API URLs to gather information or automate operations, such as scaling.
diff --git a/docker-cloud/apps/service-redeploy.md b/docker-cloud/apps/service-redeploy.md
@@ -1,9 +1,8 @@
 ---
+description: Redeploy running services
+keywords: redeploy, running, services
 redirect_from:
 - /docker-cloud/feature-reference/service-redeploy/
-description: Redeploy running services
-keywords:
-- redeploy, running, services
 title: Redeploy a running service
 ---
 
@@ -73,4 +72,4 @@ whenever a new image is pushed. See the [Autoredeploy documentation](auto-redepl
 ## Redeploy a service using webhooks
 
 You can also use **triggers** to redeploy a service, for example when its image
-is pushed or rebuilt in a third-party registry. See the [Triggers documentation](triggers.md) to learn more.
+is pushed or rebuilt in a third-party registry. See the [Triggers documentation](triggers.md) to learn more.
diff --git a/docker-cloud/apps/service-scaling.md b/docker-cloud/apps/service-scaling.md
@@ -1,9 +1,8 @@
 ---
+description: Scale your service, spawn new containers
+keywords: spawn, container, service, deploy
 redirect_from:
 - /docker-cloud/feature-reference/service-scaling/
-description: Scale your service, spawn new containers
-keywords:
-- spawn, container, service, deploy
 title: Scale your service
 ---
 
@@ -155,4 +154,4 @@ application through the CLI:
 
 ```bash
 $ docker-cloud service run --sequential [...] 
-```
+```
diff --git a/docker-cloud/apps/stack-yaml-reference.md b/docker-cloud/apps/stack-yaml-reference.md
@@ -1,9 +1,8 @@
 ---
+description: Stack YAML reference
+keywords: YAML, stack, reference
 redirect_from:
 - /docker-cloud/feature-reference/stack-yaml-reference/
-description: Stack YAML reference
-keywords:
-- YAML, stack, reference
 title: Stack file YAML reference
 ---
 
@@ -321,4 +320,4 @@ Stack files (`docker-cloud.yml`) were designed with `docker-compose.yml` in mind
 build
 external_links
 env_file
-```
+```
diff --git a/docker-cloud/apps/stacks.md b/docker-cloud/apps/stacks.md
@@ -1,9 +1,8 @@
 ---
+description: Manage service stacks
+keywords: service, stack, yaml
 redirect_from:
 - /docker-cloud/feature-reference/stacks/
-description: Manage service stacks
-keywords:
-- service, stack, yaml
 title: Manage service stacks
 ---
 
@@ -126,4 +125,4 @@ You can update a stack from a YAML file by executing:
 docker-cloud stack update -f docker-cloud.yml (uuid or name)
 ```
 
-Check our [CLI documentation](/apidocs/docker-cloud.md#stacks) for more information.
+Check our [CLI documentation](/apidocs/docker-cloud.md#stacks) for more information.
diff --git a/docker-cloud/apps/triggers.md b/docker-cloud/apps/triggers.md
@@ -1,9 +1,8 @@
 ---
+description: Use triggers
+keywords: API, triggers, endpoints
 redirect_from:
 - /docker-cloud/feature-reference/triggers/
-description: Use triggers
-keywords:
-- API, triggers, endpoints
 title: Use triggers
 ---
 
@@ -56,4 +55,4 @@ Once the trigger is revoked, it stops accepting requests.
 
 ## Using triggers in the API and CLI
 
-See our [API and CLI documentation](/apidocs/docker-cloud.md#triggers) to learn how to use triggers with our API and the CLI.
+See our [API and CLI documentation](/apidocs/docker-cloud.md#triggers) to learn how to use triggers with our API and the CLI.
diff --git a/docker-cloud/apps/volumes.md b/docker-cloud/apps/volumes.md
@@ -1,10 +1,9 @@
 ---
+description: Work with data volumes
+keywords: data, volumes, create, reuse
 redirect_from:
 - /docker-cloud/tutorials/download-volume-data/
 - /docker-cloud/feature-reference/volumes/
-description: Work with data volumes
-keywords:
-- data, volumes, create, reuse
 title: Work with data volumes
 ---
 
@@ -67,4 +66,4 @@ You might find it helpful to download or back up the data from volumes that are
 
    ```
    $ scp -r -P 2222 [email protected]:/var/lib/mysql .
-   ```
+   ```
diff --git a/docker-cloud/builds/advanced.md b/docker-cloud/builds/advanced.md
@@ -1,7 +1,6 @@
 ---
 description: Automated builds
-keywords:
-- automated, build, images
+keywords: automated, build, images
 title: Advanced options for Autobuild and Autotest
 ---
 
@@ -111,4 +110,4 @@ If you needed to give the resulting image multiple tags, or push the same image
 ```none
 docker tag $IMAGE_NAME $DOCKER_REPO:$SOURCE_COMMIT
 docker push $DOCKER_REPO:$SOURCE_COMMIT
-```
+```
diff --git a/docker-cloud/builds/automated-build.md b/docker-cloud/builds/automated-build.md
@@ -1,9 +1,8 @@
 ---
+description: Automated builds
+keywords: automated, build, images
 redirect_from:
 - /docker-cloud/feature-reference/automated-build/
-description: Automated builds
-keywords:
-- automated, build, images
 title: Automated builds
 ---
 
@@ -294,4 +293,4 @@ Docker Cloud's [Autotest](automated-testing.md) feature which
 integrates seamlessly with autobuild and autoredeploy.
 
 > **Note**: While the Autotest feature builds an image for testing purposes, it
-does not push the resulting image to Docker Cloud or the external registry.
+does not push the resulting image to Docker Cloud or the external registry.
diff --git a/docker-cloud/builds/automated-testing.md b/docker-cloud/builds/automated-testing.md
@@ -1,9 +1,8 @@
 ---
+description: Automated tests
+keywords: Automated, testing, repository
 redirect_from:
 - /docker-cloud/feature-reference/automated-testing/
-description: Automated tests
-keywords:
-- Automated, testing, repository
 title: Automated repository tests
 ---
 
@@ -92,4 +91,4 @@ From the repository's details page, click **Timeline**.
 From this tab you can see any pending, in-progress, successful, and failed
 builds and test runs for the repository.
 
-You can click any timeline entry to view the logs for each test run.
+You can click any timeline entry to view the logs for each test run.
diff --git a/docker-cloud/builds/image-scan.md b/docker-cloud/builds/image-scan.md
@@ -1,7 +1,6 @@
 ---
-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
+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
 title: Docker Security Scanning
 ---
 
@@ -181,4 +180,4 @@ components.
 ## Related information
 
 * [Learn about CVE and how it compiles data](https://cve.mitre.org/about/index.html).
-* [How to create a Docker Official image](/docker-hub/official_repos/)
+* [How to create a Docker Official image](/docker-hub/official_repos/)
diff --git a/docker-cloud/builds/index.md b/docker-cloud/builds/index.md
@@ -1,7 +1,6 @@
 ---
 description: Manage Builds and Images in Docker Cloud
-keywords:
-- builds, images, Cloud
+keywords: builds, images, Cloud
 notoc: true
 title: Builds and images overview
 ---
@@ -24,4 +23,4 @@ running services when a build passes its tests.
 * [Automated repository tests](automated-testing.md)
 * [Advanced options for Autobuild and Autotest](advanced.md)
 
-![a Docker Cloud repository's General view](images/repo-general.png)
+![a Docker Cloud repository's General view](images/repo-general.png)