From 4148feebebec37aba879d2be90e1c2d8bf2c86db Mon Sep 17 00:00:00 2001
From: Connor King <sigstackfault@gmail.com>
Date: Sun, 12 Nov 2023 11:46:24 -0500
Subject: [PATCH] use `tree` syntax to explain bevy_rock file structure

---
 crates/bevy_asset/src/io/embedded/mod.rs | 16 +++++++++-------
 1 file changed, 9 insertions(+), 7 deletions(-)

diff --git a/crates/bevy_asset/src/io/embedded/mod.rs b/crates/bevy_asset/src/io/embedded/mod.rs
index a0d95c9744f5a..f6620b3e69cec 100644
--- a/crates/bevy_asset/src/io/embedded/mod.rs
+++ b/crates/bevy_asset/src/io/embedded/mod.rs
@@ -131,13 +131,15 @@ macro_rules! embedded_path {
 /// For example, consider the following file structure in the theoretical `bevy_rock` crate, which provides a Bevy [`Plugin`](bevy_app::Plugin)
 /// that renders fancy rocks for scenes.
 ///
-/// * `bevy_rock`
-///     * `src`
-///         * `render`
-///             * `rock.wgsl`
-///             * `mod.rs`
-///         * `lib.rs`
-///     * `Cargo.toml`
+/// ```text
+/// bevy_rock
+/// ├── src
+/// │   ├── render
+/// │   │   ├── rock.wgsl
+/// │   │   └── mod.rs
+/// │   └── lib.rs
+/// └── Cargo.toml
+/// ```
 ///
 /// `rock.wgsl` is a WGSL shader asset that the `bevy_rock` plugin author wants to bundle with their crate. They invoke the following
 /// in `bevy_rock/src/render/mod.rs`: