Merge commit '35dec7c96f7ee3eb17dd444f7067f0c776fb56ae'

docs/content/en/content-management/page-bundles.md

@@ -1,14 +1,14 @@
 ---
 title: Page bundles
 description: Content organization using Page Bundles
-keywords: [page, bundle, leaf, branch]
 categories: [content management]
+keywords: [page,bundle,leaf,branch]
 menu :
   docs:
     parent: content-management
     weight: 30
-toc: true
 weight: 30
+toc: true
 ---
 
 Page Bundles are a way to group [Page Resources](/content-management/page-resources/).
@@ -48,24 +48,24 @@ content/
 │   │   ├── image2.png
 │   │   └── index.md
 │   └── my-other-post
-│       └── index.md
+│       └── index.md
 │
 └── another-section
     ├── ..
-    └── not-a-leaf-bundle
+    └── not-a-leaf-bundle
         ├── ..
-        └── another-leaf-bundle
-            └── index.md
+        └── another-leaf-bundle
+            └── index.md
 ```
 
 In the above example `content/` directory, there are four leaf
 bundles:
 
-`about`
+about
 : This leaf bundle is at the root level (directly under
     `content` directory) and has only the `index.md`.
 
-`my-post`
+my-post
 : This leaf bundle has the `index.md`, two other content
     Markdown files and two image files.
 
@@ -78,10 +78,10 @@ These content files are page resources of `my-post`
     and only available in `my-post/index.md` resources.
     They will **not** be rendered as individual pages.
 
-`my-other-post`
+my-other-post
 : This leaf bundle has only the `index.md`.
 
-`another-leaf-bundle`
+another-leaf-bundle
 : This leaf bundle is nested under couple of
     directories. This bundle also has only the `index.md`.
 
@@ -90,7 +90,6 @@ The hierarchy depth at which a leaf bundle is created does not matter,
 as long as it is not inside another **leaf** bundle.
 {{% /note %}}
 
-
 ### Headless bundle
 
 A headless bundle is a bundle that is configured to not get published
@@ -128,7 +127,7 @@ Explanation of the above example:
 A leaf bundle can be made headless by adding below in the front matter
 (in the `index.md`):
 
-{{< code-toggle file="content/headless/index.md" fm=true copy=false >}}
+{{< code-toggle file=content/headless/index.md fm=true >}}
 headless = true
 {{< /code-toggle >}}
 
@@ -149,17 +148,16 @@ Here `md` (markdown) is used just as an example. You can use any file
 type as a content resource as long as it is a content type recognized by Hugo.
 {{% /note %}}
 
-
 ### Examples of branch bundle organization
 
 ```text
 content/
 ├── branch-bundle-1
-│   ├── branch-content1.md
-│   ├── branch-content2.md
-│   ├── image1.jpg
-│   ├── image2.png
-│   └── _index.md
+│   ├── branch-content1.md
+│   ├── branch-content2.md
+│   ├── image1.jpg
+│   ├── image2.png
+│   └── _index.md
 └── branch-bundle-2
     ├── _index.md
     └── a-leaf-bundle
@@ -169,11 +167,11 @@ content/
 In the above example `content/` directory, there are two branch
 bundles (and a leaf bundle):
 
-`branch-bundle-1`
+branch-bundle-1
 : This branch bundle has the `_index.md`, two
     other content Markdown files and two image files.
 
-`branch-bundle-2`
+branch-bundle-2
 : This branch bundle has the `_index.md` and a
     nested leaf bundle.