From 792173632d7bff3eb9f302cbed160a8cd886f09f Mon Sep 17 00:00:00 2001 From: Gareth Dwyer Date: Sun, 29 Jan 2023 13:10:15 +0200 Subject: [PATCH] Documentation (#4937) --- docs/setup/setting-up-navigation.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/setup/setting-up-navigation.md b/docs/setup/setting-up-navigation.md index 7ed0bf074..ed81f698e 100644 --- a/docs/setup/setting-up-navigation.md +++ b/docs/setup/setting-up-navigation.md @@ -3,7 +3,7 @@ A clear and concise navigation structure is an important aspect of good project documentation. Material for MkDocs provides a multitude of options to configure the behavior of navigational elements, including [tabs] and [sections], and one -of its flag-ship feature: [instant loading]. +of its flagship features: [instant loading]. [tabs]: #navigation-tabs [sections]: #navigation-sections @@ -63,7 +63,7 @@ the following lines to `mkdocs.yml`: [^1]: Prior to :octicons-tag-24: 6.2.0, navigation tabs had a slightly different behavior. All top-level pages (i.e. all top-level entries directly - refefring to a `*.md` file) defined inside the `nav` entry of `mkdocs.yml` + referring to a `*.md` file) defined inside the `nav` entry of `mkdocs.yml` were grouped under the first tab which received the title of the first page. This made it impossible to include a top-level page (or external link) as a tab item, as was reported in #1884 and #2072. From :octicons-tag-24: 6.2.0