From 6c728120beeb363d59cd1adedb8d174840216ef9 Mon Sep 17 00:00:00 2001 From: Krzysztof Szafranek Date: Tue, 23 May 2017 08:47:39 +0200 Subject: [PATCH] Use more precise language when explaining links (#6078) Merge pull request 6078 --- docs/_docs/templates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/_docs/templates.md b/docs/_docs/templates.md index c612df49..cc21b36b 100644 --- a/docs/_docs/templates.md +++ b/docs/_docs/templates.md @@ -542,7 +542,7 @@ You can also use the `link` tag to create a link in Markdown as follows: The path to the post, page, or collection is defined as the path relative to the root directory (where your config file is) to the file, not the path from your existing page to the other page. -For example, suppose you're creating a link `page_a.md` (stored in `pages/folder1/folder2`) to `page_b.md` (stored in `pages/folder1`). Your path in the link would not be `../page_b.html`. Instead, it would be `/pages/folder1/page_b.md`. +For example, suppose you're creating a link in `page_a.md` (stored in `pages/folder1/folder2`) to `page_b.md` (stored in `pages/folder1`). Your path in the link would not be `../page_b.html`. Instead, it would be `/pages/folder1/page_b.md`. If you're unsure of the path, add `{% raw %}{{ page.path }}{% endraw %}` to the page and it will display the path.