diff --git a/content/patterns/coding/file-trees.md b/content/patterns/coding/file-trees.md
index 8913a29..dc0fd68 100644
--- a/content/patterns/coding/file-trees.md
+++ b/content/patterns/coding/file-trees.md
@@ -17,10 +17,13 @@ The file tree is described using a markdown nested list structure:
* Level 3 folder
* Level 4 file
* Level 4 file
+ * Level 3 file
* Level 2 folder
* Level 3 file
* Level 3 file
* Level 3 file
+ * Level 2 file
+* Level 1 file
{{% /fileTree %}}
{{}}
@@ -36,6 +39,7 @@ This is drawn in the following fashion, but preserves the underlying nested list
* Level 3 folder
* Level 4 file
* Level 4 file
+ * Level 3 file
* Level 2 folder
* Level 3 file
* Level 3 file
@@ -45,5 +49,5 @@ This is drawn in the following fashion, but preserves the underlying nested list
{{% /fileTree %}}
{{% warning %}}
-The only reliable way to nest unordered lists in markdown is to indent the nested item by exactly four spaces. Using tabs and less than four spaces are unreliable methods.
+The only reliable way to nest unordered lists in markdown is to indent the nested item by exactly four spaces. Using tabs or less than four spaces are unreliable methods.
{{% /warning %}}
diff --git a/docs/index.xml b/docs/index.xml
index 20ab453..97941b6 100644
--- a/docs/index.xml
+++ b/docs/index.xml
@@ -106,7 +106,7 @@ npm run start The cmd shortcode currently only supports single commands. If y
https://heydon.github.io/infusion/patterns/coding/file-trees/Representing folder/file structures is simple and accessible in Infusion. Which is just as well, because some components may need to conform to a certain folder structure.
The file tree is described using a markdown nested list structure:
-{{% fileTree %}} * Level 1 folder * Level 2 file * Level 2 folder * Level 3 file * Level 3 folder * Level 4 file * Level 3 folder * Level 4 file * Level 4 file * Level 2 folder * Level 3 file * Level 3 file * Level 3 file {{% /fileTree %}} This is drawn in the following fashion, but preserves the underlying nested list structure for assistive technologies such as screen readers:
+{{% fileTree %}} * Level 1 folder * Level 2 file * Level 2 folder * Level 3 file * Level 3 folder * Level 4 file * Level 3 folder * Level 4 file * Level 4 file * Level 3 file * Level 2 folder * Level 3 file * Level 3 file * Level 3 file * Level 2 file * Level 1 file {{% /fileTree %}} This is drawn in the following fashion, but preserves the underlying nested list structure for assistive technologies such as screen readers:
diff --git a/docs/patterns/coding/file-trees/index.html b/docs/patterns/coding/file-trees/index.html
index ec85d6d..9714920 100644
--- a/docs/patterns/coding/file-trees/index.html
+++ b/docs/patterns/coding/file-trees/index.html
@@ -294,10 +294,13 @@
* Level 3 folder
* Level 4 file
* Level 4 file
+ * Level 3 file
* Level 2 folder
* Level 3 file
* Level 3 file
* Level 3 file
+ * Level 2 file
+* Level 1 file
{{% /fileTree %}}
@@ -325,6 +328,7 @@
Level 4 file
Level 4 file
+
Level 3 file
Level 2 folder
@@ -346,7 +350,7 @@
-
The only reliable way to nest unordered lists in markdown is to indent the nested item by exactly four spaces. Using tabs and less than four spaces are unreliable methods.
+
The only reliable way to nest unordered lists in markdown is to indent the nested item by exactly four spaces. Using tabs or less than four spaces are unreliable methods.
diff --git a/docs/patterns/coding/index.xml b/docs/patterns/coding/index.xml
index 3928092..e8db521 100644
--- a/docs/patterns/coding/index.xml
+++ b/docs/patterns/coding/index.xml
@@ -74,7 +74,7 @@ npm run start The cmd shortcode currently only supports single commands. If y
https://heydon.github.io/infusion/patterns/coding/file-trees/Representing folder/file structures is simple and accessible in Infusion. Which is just as well, because some components may need to conform to a certain folder structure.
The file tree is described using a markdown nested list structure:
-{{% fileTree %}} * Level 1 folder * Level 2 file * Level 2 folder * Level 3 file * Level 3 folder * Level 4 file * Level 3 folder * Level 4 file * Level 4 file * Level 2 folder * Level 3 file * Level 3 file * Level 3 file {{% /fileTree %}} This is drawn in the following fashion, but preserves the underlying nested list structure for assistive technologies such as screen readers:
+{{% fileTree %}} * Level 1 folder * Level 2 file * Level 2 folder * Level 3 file * Level 3 folder * Level 4 file * Level 3 folder * Level 4 file * Level 4 file * Level 3 file * Level 2 folder * Level 3 file * Level 3 file * Level 3 file * Level 2 file * Level 1 file {{% /fileTree %}} This is drawn in the following fashion, but preserves the underlying nested list structure for assistive technologies such as screen readers: