From a5f5875ea34c047edcc8bd9c7a3962da08a9c78d Mon Sep 17 00:00:00 2001 From: Victoria Bialas Date: Wed, 26 Apr 2017 13:19:51 -0700 Subject: [PATCH] fix glossary instructions (#3084) * fix glossary instructions Signed-off-by: Victoria Bialas corrected links Signed-off-by: Victoria Bialas * copyedits Signed-off-by: Victoria Bialas --- test.md | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/test.md b/test.md index c55015d6ca..b184267cb0 100644 --- a/test.md +++ b/test.md @@ -185,14 +185,17 @@ only need to do it on the first one. If you have a ``, set it there. -## Update or link to the Glossary +## Glossary -The glossary source lives in the documentation repository https://github.com/docker/docker.github.io in `_data/glossary.yaml`. The glossary publishes to [https://docs.docker.com/glossary/](https://docs.docker.com/glossary/), but is linkable in documentation markdown files at `/engine/reference/glossary.md`. +The glossary source lives in the documentation repository +https://github.com/docker/docker.github.io in `_data/glossary.yaml`. The +glossary publishes to +[https://docs.docker.com/glossary/](https://docs.docker.com/glossary/). -To update glossary content, edit `_data/glossary.yaml` in . - -To link to a glossary term, link to `/engine/reference/glossary.md#YourGlossaryTerm` (for example, `/engine/reference/glossary.md#swarm`). +To update glossary content, edit `_data/glossary.yaml`. +To link to a glossary term, link to `glossary.md?term=YourGlossaryTerm` (for +example, [swarm](glossary.md?term=swarm)). ## Mixing Markdown and HTML