diff --git a/R/tar_repository_cas.R b/R/tar_repository_cas.R
index c3d28e58..090d7a8c 100644
--- a/R/tar_repository_cas.R
+++ b/R/tar_repository_cas.R
@@ -16,10 +16,10 @@
#'
#' ```
#' _targets/
-#' ├── meta/
-#' │ └── meta
-#' └── objects/
-#' └── x
+#' meta/
+#' meta
+#' objects/
+#' x
#' ```
#'
#' By contrast, with content-addressable storage (CAS),
@@ -34,12 +34,12 @@
#'
#' ```
#' _targets/
-#' └── meta/
-#' └── meta
+#' meta/
+#' meta
#' my_cas/
-#' ├── 1fffeb09ad36e84a
-#' ├── 68328d833e6361d3
-#' └── 798af464fb2f6b30
+#' 1fffeb09ad36e84a
+#' 68328d833e6361d3
+#' 798af464fb2f6b30
#' ```
#'
#' The next call to `tar_read(x)` uses `tar_meta(x)$data`
diff --git a/man/tar_repository_cas.Rd b/man/tar_repository_cas.Rd
index d866fc8f..6b007ef0 100644
--- a/man/tar_repository_cas.Rd
+++ b/man/tar_repository_cas.Rd
@@ -114,10 +114,10 @@ In other words, no matter how many changes happen to \code{x},
the data store always looks like this:
\if{html}{\out{
}}\preformatted{_targets/
-├── meta/
-│ └── meta
-└── objects/
- └── x
+ meta/
+ meta
+ objects/
+ x
}\if{html}{\out{
}}
By contrast, with content-addressable storage (CAS),
@@ -131,12 +131,12 @@ in that folder. If you run \code{\link[=tar_make]{tar_make()}} three different t
with three different values of \code{x}, then storage will look like this:
\if{html}{\out{}}\preformatted{_targets/
-└── meta/
- └── meta
+ meta/
+ meta
my_cas/
-├── 1fffeb09ad36e84a
-├── 68328d833e6361d3
-└── 798af464fb2f6b30
+ 1fffeb09ad36e84a
+ 68328d833e6361d3
+ 798af464fb2f6b30
}\if{html}{\out{
}}
The next call to \code{tar_read(x)} uses \code{tar_meta(x)$data}
diff --git a/man/tar_repository_cas_local.Rd b/man/tar_repository_cas_local.Rd
index 33cefbdb..f068885f 100644
--- a/man/tar_repository_cas_local.Rd
+++ b/man/tar_repository_cas_local.Rd
@@ -63,10 +63,10 @@ In other words, no matter how many changes happen to \code{x},
the data store always looks like this:
\if{html}{\out{}}\preformatted{_targets/
-├── meta/
-│ └── meta
-└── objects/
- └── x
+ meta/
+ meta
+ objects/
+ x
}\if{html}{\out{
}}
By contrast, with content-addressable storage (CAS),
@@ -80,12 +80,12 @@ in that folder. If you run \code{\link[=tar_make]{tar_make()}} three different t
with three different values of \code{x}, then storage will look like this:
\if{html}{\out{}}\preformatted{_targets/
-└── meta/
- └── meta
+ meta/
+ meta
my_cas/
-├── 1fffeb09ad36e84a
-├── 68328d833e6361d3
-└── 798af464fb2f6b30
+ 1fffeb09ad36e84a
+ 68328d833e6361d3
+ 798af464fb2f6b30
}\if{html}{\out{
}}
The next call to \code{tar_read(x)} uses \code{tar_meta(x)$data}
diff --git a/man/tar_repository_cas_local_gc.Rd b/man/tar_repository_cas_local_gc.Rd
index e462bc3b..94fc21e3 100644
--- a/man/tar_repository_cas_local_gc.Rd
+++ b/man/tar_repository_cas_local_gc.Rd
@@ -50,10 +50,10 @@ In other words, no matter how many changes happen to \code{x},
the data store always looks like this:
\if{html}{\out{}}\preformatted{_targets/
-├── meta/
-│ └── meta
-└── objects/
- └── x
+ meta/
+ meta
+ objects/
+ x
}\if{html}{\out{
}}
By contrast, with content-addressable storage (CAS),
@@ -67,12 +67,12 @@ in that folder. If you run \code{\link[=tar_make]{tar_make()}} three different t
with three different values of \code{x}, then storage will look like this:
\if{html}{\out{}}\preformatted{_targets/
-└── meta/
- └── meta
+ meta/
+ meta
my_cas/
-├── 1fffeb09ad36e84a
-├── 68328d833e6361d3
-└── 798af464fb2f6b30
+ 1fffeb09ad36e84a
+ 68328d833e6361d3
+ 798af464fb2f6b30
}\if{html}{\out{
}}
The next call to \code{tar_read(x)} uses \code{tar_meta(x)$data}