From 9a2b2ef92c0a75327f0b3a218f8f0fa8799e7223 Mon Sep 17 00:00:00 2001 From: Caen De Silva Date: Fri, 12 Jul 2024 14:43:13 +0200 Subject: [PATCH] Fix punctuation --- docs/creating-content/documentation-pages.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/creating-content/documentation-pages.md b/docs/creating-content/documentation-pages.md index 6d94081a09c..429c52fdf02 100644 --- a/docs/creating-content/documentation-pages.md +++ b/docs/creating-content/documentation-pages.md @@ -146,7 +146,7 @@ navigation: You can also automatically group your documentation pages by placing source files in sub-directories. -For example, putting a Markdown file in `_docs/getting-started/`, is equivalent to adding the same front matter seen above. +For example, putting a Markdown file in `_docs/getting-started/` is equivalent to adding the same front matter seen above. >info Note that when the [flattened output paths](#using-flattened-output-paths) setting is enabled (which it is by default), the file will still be compiled to the `_site/docs/` directory like it would be if you didn't use the subdirectories. Note that this means that you can't have two documentation pages with the same filename as they overwrite each other.