From 540c59ce7d9ab243d3c8515e2691a8d6af663c80 Mon Sep 17 00:00:00 2001
From: Brian MacKinney <bmackinney@gmail.com>
Date: Sat, 5 Oct 2019 02:21:08 -0700
Subject: [PATCH] Clarify config directory structure

---
 content/en/getting-started/configuration.md | 26 ++++++++++-----------
 1 file changed, 13 insertions(+), 13 deletions(-)

diff --git a/content/en/getting-started/configuration.md b/content/en/getting-started/configuration.md
index 2e1d14137..0961b4b95 100644
--- a/content/en/getting-started/configuration.md
+++ b/content/en/getting-started/configuration.md
@@ -50,19 +50,19 @@ In addition to using a single site config file, one can use the `configDir` dire
 
 
 ```
-config
-├── _default
-│   ├── config.toml
-│   ├── languages.toml
-│   ├── menus.en.toml
-│   ├── menus.zh.toml
-│   └── params.toml
-├── staging
-│   ├── config.toml
-│   └── params.toml
-└── production
-    ├── config.toml
-    └── params.toml
+├── config
+│   ├── _default
+│   │   ├── config.toml
+│   │   ├── languages.toml
+│   │   ├── menus.en.toml
+│   │   ├── menus.zh.toml
+│   │   └── params.toml
+│   ├── production
+│   │   ├── config.toml
+│   │   └── params.toml
+│   └── staging
+│       ├── config.toml
+│       └── params.toml
 ```
 
 Considering the structure above, when running `hugo --environment staging`, Hugo will use every settings from `config/_default` and merge `staging`'s on top of those.