diff --git a/concepts/build-files.mdx b/concepts/build-files.mdx
index ec87f4db..b85f472c 100644
--- a/concepts/build-files.mdx
+++ b/concepts/build-files.mdx
@@ -132,23 +132,6 @@ for anyone to create new rules.
and binaries and tests can depend on libraries, with the expected
separate-compilation behavior.
-
-
## File encoding
`BUILD` and `.bzl` files should be encoded in UTF-8, of which ASCII is a valid
diff --git a/concepts/build-ref.mdx b/concepts/build-ref.mdx
index 0af78970..67c5f1bd 100644
--- a/concepts/build-ref.mdx
+++ b/concepts/build-ref.mdx
@@ -99,7 +99,3 @@ package groups they include. The only allowed ways to refer to them are from the
the `package` function; they do not generate or consume files. For more
information, refer to the [`package_group`
documentation](/reference/be/functions#package_group).
-
-
- Labelsarrow_forward
-
diff --git a/concepts/dependencies.mdx b/concepts/dependencies.mdx
index 39fef86e..e03c1af7 100644
--- a/concepts/dependencies.mdx
+++ b/concepts/dependencies.mdx
@@ -366,21 +366,3 @@ filegroup(
```
You can then reference the label `my_data` as the data dependency in your test.
-
-
-
diff --git a/concepts/labels.mdx b/concepts/labels.mdx
index 5b0b1c6a..aec9adcf 100644
--- a/concepts/labels.mdx
+++ b/concepts/labels.mdx
@@ -241,20 +241,3 @@ the build.
This directed acyclic graph over targets is called the _target graph_ or
_build dependency graph_, and is the domain over which the
[Bazel Query tool](/query/guide) operates.
-
-
diff --git a/remote/caching.mdx b/remote/caching.mdx
index 09774d21..ffe30ed9 100644
--- a/remote/caching.mdx
+++ b/remote/caching.mdx
@@ -129,7 +129,7 @@ not provide technical support for bazel-remote.
This cache stores contents on disk and also provides garbage collection
to enforce an upper storage limit and clean unused artifacts. The cache is
-available as a [docker image] and its code is available on
+available as a [docker image](https://hub.docker.com/r/buchgr/bazel-remote-cache/) and its code is available on
[GitHub](https://github.com/buchgr/bazel-remote/).
Both the REST and gRPC remote cache APIs are supported.
diff --git a/upstream b/upstream
index 95ce4c19..d294eaa5 160000
--- a/upstream
+++ b/upstream
@@ -1 +1 @@
-Subproject commit 95ce4c19632621cbe776d7b82bbb793fe584cb87
+Subproject commit d294eaa5881ae3fc489fc41a2cda45fd7cd03073
diff --git a/versions/6.5.0/concepts/build-files.mdx b/versions/6.5.0/concepts/build-files.mdx
index b468b9f9..b05e79e0 100644
--- a/versions/6.5.0/concepts/build-files.mdx
+++ b/versions/6.5.0/concepts/build-files.mdx
@@ -125,10 +125,3 @@ for anyone to create new rules.
programming language. Libraries can depend on other libraries,
and binaries and tests can depend on libraries, with the expected
separate-compilation behavior.
-
-
diff --git a/versions/6.5.0/concepts/build-ref.mdx b/versions/6.5.0/concepts/build-ref.mdx
index b7f338ee..3cc6bf3a 100644
--- a/versions/6.5.0/concepts/build-ref.mdx
+++ b/versions/6.5.0/concepts/build-ref.mdx
@@ -109,7 +109,3 @@ package groups they include. The only allowed ways to refer to them are from the
the `package` function; they do not generate or consume files. For more
information, refer to the [`package_group`
documentation](/reference/be/functions#package_group).
-
-
- Labelsarrow_forward
-
diff --git a/versions/6.5.0/concepts/dependencies.mdx b/versions/6.5.0/concepts/dependencies.mdx
index 52f28620..345b6246 100644
--- a/versions/6.5.0/concepts/dependencies.mdx
+++ b/versions/6.5.0/concepts/dependencies.mdx
@@ -344,11 +344,3 @@ filegroup(
```
You can then reference the label `my_data` as the data dependency in your test.
-
-
-
diff --git a/versions/6.5.0/concepts/labels.mdx b/versions/6.5.0/concepts/labels.mdx
index 286804f7..c1506361 100644
--- a/versions/6.5.0/concepts/labels.mdx
+++ b/versions/6.5.0/concepts/labels.mdx
@@ -212,10 +212,3 @@ the build.
This directed acyclic graph over targets is called the _target graph_ or
_build dependency graph_, and is the domain over which the
[Bazel Query tool](/versions/6.5.0/docs/query-how-to) operates.
-
-
diff --git a/versions/6.5.0/remote/caching.mdx b/versions/6.5.0/remote/caching.mdx
index 64611b18..a4fff2ee 100644
--- a/versions/6.5.0/remote/caching.mdx
+++ b/versions/6.5.0/remote/caching.mdx
@@ -128,7 +128,7 @@ not provide technical support for bazel-remote.
This cache stores contents on disk and also provides garbage collection
to enforce an upper storage limit and clean unused artifacts. The cache is
-available as a [docker image] and its code is available on
+available as a [docker image](https://hub.docker.com/r/buchgr/bazel-remote-cache/) and its code is available on
[GitHub](https://github.com/buchgr/bazel-remote/).
Both the REST and gRPC remote cache APIs are supported.
diff --git a/versions/6.5.0/versions/index.mdx b/versions/6.5.0/versions/index.mdx
index f71981be..09904b7e 100644
--- a/versions/6.5.0/versions/index.mdx
+++ b/versions/6.5.0/versions/index.mdx
@@ -10,7 +10,3 @@ version support.
For now, to see documentation for older Bazel versions, go to
[docs.bazel.build](https://docs.bazel.build/).
-
-
- To the Archives!arrow_forward
-
diff --git a/versions/7.6.1/concepts/build-files.mdx b/versions/7.6.1/concepts/build-files.mdx
index 4e4473fc..010e0491 100644
--- a/versions/7.6.1/concepts/build-files.mdx
+++ b/versions/7.6.1/concepts/build-files.mdx
@@ -132,10 +132,3 @@ for anyone to create new rules.
programming language. Libraries can depend on other libraries,
and binaries and tests can depend on libraries, with the expected
separate-compilation behavior.
-
-
diff --git a/versions/7.6.1/concepts/build-ref.mdx b/versions/7.6.1/concepts/build-ref.mdx
index 911028a7..177b315b 100644
--- a/versions/7.6.1/concepts/build-ref.mdx
+++ b/versions/7.6.1/concepts/build-ref.mdx
@@ -97,7 +97,3 @@ package groups they include. The only allowed ways to refer to them are from the
the `package` function; they do not generate or consume files. For more
information, refer to the [`package_group`
documentation](/versions/7.6.1/reference/be/functions#package_group).
-
-
- Labelsarrow_forward
-
\ No newline at end of file
diff --git a/versions/7.6.1/concepts/dependencies.mdx b/versions/7.6.1/concepts/dependencies.mdx
index 0c92f1ea..0b526039 100644
--- a/versions/7.6.1/concepts/dependencies.mdx
+++ b/versions/7.6.1/concepts/dependencies.mdx
@@ -347,8 +347,3 @@ filegroup(
```
You can then reference the label `my_data` as the data dependency in your test.
-
-
-
diff --git a/versions/7.6.1/concepts/labels.mdx b/versions/7.6.1/concepts/labels.mdx
index 60891bc7..8ed20174 100644
--- a/versions/7.6.1/concepts/labels.mdx
+++ b/versions/7.6.1/concepts/labels.mdx
@@ -228,10 +228,3 @@ the build.
This directed acyclic graph over targets is called the _target graph_ or
_build dependency graph_, and is the domain over which the
[Bazel Query tool](/versions/7.6.1/query/guide) operates.
-
-
diff --git a/versions/7.6.1/remote/caching.mdx b/versions/7.6.1/remote/caching.mdx
index 587c3d9a..1b4e05ec 100644
--- a/versions/7.6.1/remote/caching.mdx
+++ b/versions/7.6.1/remote/caching.mdx
@@ -126,7 +126,7 @@ not provide technical support for bazel-remote.
This cache stores contents on disk and also provides garbage collection
to enforce an upper storage limit and clean unused artifacts. The cache is
-available as a [docker image] and its code is available on
+available as a [docker image](https://hub.docker.com/r/buchgr/bazel-remote-cache/) and its code is available on
[GitHub](https://github.com/buchgr/bazel-remote/).
Both the REST and gRPC remote cache APIs are supported.
diff --git a/versions/7.6.1/versions/index.mdx b/versions/7.6.1/versions/index.mdx
index c92a15b6..ad1492e5 100644
--- a/versions/7.6.1/versions/index.mdx
+++ b/versions/7.6.1/versions/index.mdx
@@ -11,7 +11,3 @@ version support.
For now, to see documentation for older Bazel versions, go to
[docs.bazel.build](https://docs.bazel.build/).
-
-
- To the Archives!arrow_forward
-
diff --git a/versions/7.7.1/concepts/build-files.mdx b/versions/7.7.1/concepts/build-files.mdx
index bcd6ef60..819f2374 100644
--- a/versions/7.7.1/concepts/build-files.mdx
+++ b/versions/7.7.1/concepts/build-files.mdx
@@ -132,10 +132,3 @@ for anyone to create new rules.
programming language. Libraries can depend on other libraries,
and binaries and tests can depend on libraries, with the expected
separate-compilation behavior.
-
-
diff --git a/versions/7.7.1/concepts/build-ref.mdx b/versions/7.7.1/concepts/build-ref.mdx
index b2b952a6..c8d6b6d8 100644
--- a/versions/7.7.1/concepts/build-ref.mdx
+++ b/versions/7.7.1/concepts/build-ref.mdx
@@ -97,7 +97,3 @@ package groups they include. The only allowed ways to refer to them are from the
the `package` function; they do not generate or consume files. For more
information, refer to the [`package_group`
documentation](/versions/7.7.1/reference/be/functions#package_group).
-
-
- Labelsarrow_forward
-
\ No newline at end of file
diff --git a/versions/7.7.1/concepts/dependencies.mdx b/versions/7.7.1/concepts/dependencies.mdx
index 0df26784..3358c7c1 100644
--- a/versions/7.7.1/concepts/dependencies.mdx
+++ b/versions/7.7.1/concepts/dependencies.mdx
@@ -325,11 +325,3 @@ filegroup(
```
You can then reference the label `my_data` as the data dependency in your test.
-
-
-
diff --git a/versions/7.7.1/concepts/labels.mdx b/versions/7.7.1/concepts/labels.mdx
index 520dfec2..9780c61c 100644
--- a/versions/7.7.1/concepts/labels.mdx
+++ b/versions/7.7.1/concepts/labels.mdx
@@ -228,10 +228,3 @@ the build.
This directed acyclic graph over targets is called the _target graph_ or
_build dependency graph_, and is the domain over which the
[Bazel Query tool](/versions/7.7.1/query/guide) operates.
-
-
diff --git a/versions/7.7.1/remote/caching.mdx b/versions/7.7.1/remote/caching.mdx
index 5a52f250..8ee01652 100644
--- a/versions/7.7.1/remote/caching.mdx
+++ b/versions/7.7.1/remote/caching.mdx
@@ -126,7 +126,7 @@ not provide technical support for bazel-remote.
This cache stores contents on disk and also provides garbage collection
to enforce an upper storage limit and clean unused artifacts. The cache is
-available as a [docker image] and its code is available on
+available as a [docker image](https://hub.docker.com/r/buchgr/bazel-remote-cache/) and its code is available on
[GitHub](https://github.com/buchgr/bazel-remote/).
Both the REST and gRPC remote cache APIs are supported.
diff --git a/versions/8.0.1/concepts/build-files.mdx b/versions/8.0.1/concepts/build-files.mdx
index 662aec5e..7e730fd3 100644
--- a/versions/8.0.1/concepts/build-files.mdx
+++ b/versions/8.0.1/concepts/build-files.mdx
@@ -132,12 +132,3 @@ for anyone to create new rules.
programming language. Libraries can depend on other libraries,
and binaries and tests can depend on libraries, with the expected
separate-compilation behavior.
-
-
diff --git a/versions/8.0.1/concepts/build-ref.mdx b/versions/8.0.1/concepts/build-ref.mdx
index 130ec5e5..fdcaa2fe 100644
--- a/versions/8.0.1/concepts/build-ref.mdx
+++ b/versions/8.0.1/concepts/build-ref.mdx
@@ -97,7 +97,3 @@ package groups they include. The only allowed ways to refer to them are from the
the `package` function; they do not generate or consume files. For more
information, refer to the [`package_group`
documentation](/versions/8.0.1/reference/be/functions#package_group).
-
-
- Labelsarrow_forward
-
\ No newline at end of file
diff --git a/versions/8.0.1/concepts/dependencies.mdx b/versions/8.0.1/concepts/dependencies.mdx
index 0bc129e6..5711e4fc 100644
--- a/versions/8.0.1/concepts/dependencies.mdx
+++ b/versions/8.0.1/concepts/dependencies.mdx
@@ -296,13 +296,3 @@ filegroup(
```
You can then reference the label `my_data` as the data dependency in your test.
-
-
-
diff --git a/versions/8.0.1/concepts/labels.mdx b/versions/8.0.1/concepts/labels.mdx
index f02c9395..d62146ab 100644
--- a/versions/8.0.1/concepts/labels.mdx
+++ b/versions/8.0.1/concepts/labels.mdx
@@ -239,12 +239,3 @@ the build.
This directed acyclic graph over targets is called the _target graph_ or
_build dependency graph_, and is the domain over which the
[Bazel Query tool](/versions/8.0.1/query/guide) operates.
-
-
diff --git a/versions/8.0.1/remote/caching.mdx b/versions/8.0.1/remote/caching.mdx
index 5785ff88..0216a2b6 100644
--- a/versions/8.0.1/remote/caching.mdx
+++ b/versions/8.0.1/remote/caching.mdx
@@ -126,7 +126,7 @@ not provide technical support for bazel-remote.
This cache stores contents on disk and also provides garbage collection
to enforce an upper storage limit and clean unused artifacts. The cache is
-available as a [docker image] and its code is available on
+available as a [docker image](https://hub.docker.com/r/buchgr/bazel-remote-cache/) and its code is available on
[GitHub](https://github.com/buchgr/bazel-remote/).
Both the REST and gRPC remote cache APIs are supported.
diff --git a/versions/8.1.1/concepts/build-files.mdx b/versions/8.1.1/concepts/build-files.mdx
index 06216bf4..6e745390 100644
--- a/versions/8.1.1/concepts/build-files.mdx
+++ b/versions/8.1.1/concepts/build-files.mdx
@@ -132,10 +132,3 @@ for anyone to create new rules.
programming language. Libraries can depend on other libraries,
and binaries and tests can depend on libraries, with the expected
separate-compilation behavior.
-
-
diff --git a/versions/8.1.1/concepts/build-ref.mdx b/versions/8.1.1/concepts/build-ref.mdx
index 5dce01e8..0625e6f9 100644
--- a/versions/8.1.1/concepts/build-ref.mdx
+++ b/versions/8.1.1/concepts/build-ref.mdx
@@ -97,7 +97,3 @@ package groups they include. The only allowed ways to refer to them are from the
the `package` function; they do not generate or consume files. For more
information, refer to the [`package_group`
documentation](/versions/8.1.1/reference/be/functions#package_group).
-
-
- Labelsarrow_forward
-
\ No newline at end of file
diff --git a/versions/8.1.1/concepts/dependencies.mdx b/versions/8.1.1/concepts/dependencies.mdx
index dcf79caa..ec900637 100644
--- a/versions/8.1.1/concepts/dependencies.mdx
+++ b/versions/8.1.1/concepts/dependencies.mdx
@@ -337,10 +337,3 @@ filegroup(
```
You can then reference the label `my_data` as the data dependency in your test.
-
-
diff --git a/versions/8.1.1/concepts/labels.mdx b/versions/8.1.1/concepts/labels.mdx
index 8dd577c6..066aa383 100644
--- a/versions/8.1.1/concepts/labels.mdx
+++ b/versions/8.1.1/concepts/labels.mdx
@@ -239,10 +239,3 @@ the build.
This directed acyclic graph over targets is called the _target graph_ or
_build dependency graph_, and is the domain over which the
[Bazel Query tool](/versions/8.1.1/query/guide) operates.
-
-
diff --git a/versions/8.1.1/remote/caching.mdx b/versions/8.1.1/remote/caching.mdx
index 7a7b4f2e..16741bf2 100644
--- a/versions/8.1.1/remote/caching.mdx
+++ b/versions/8.1.1/remote/caching.mdx
@@ -126,7 +126,7 @@ not provide technical support for bazel-remote.
This cache stores contents on disk and also provides garbage collection
to enforce an upper storage limit and clean unused artifacts. The cache is
-available as a [docker image] and its code is available on
+available as a [docker image](https://hub.docker.com/r/buchgr/bazel-remote-cache/) and its code is available on
[GitHub](https://github.com/buchgr/bazel-remote/).
Both the REST and gRPC remote cache APIs are supported.
diff --git a/versions/8.2.1/concepts/build-files.mdx b/versions/8.2.1/concepts/build-files.mdx
index b315f07b..3fbbba98 100644
--- a/versions/8.2.1/concepts/build-files.mdx
+++ b/versions/8.2.1/concepts/build-files.mdx
@@ -132,20 +132,3 @@ for anyone to create new rules.
programming language. Libraries can depend on other libraries,
and binaries and tests can depend on libraries, with the expected
separate-compilation behavior.
-
-
diff --git a/versions/8.2.1/concepts/build-ref.mdx b/versions/8.2.1/concepts/build-ref.mdx
index 9d2783cf..a6501030 100644
--- a/versions/8.2.1/concepts/build-ref.mdx
+++ b/versions/8.2.1/concepts/build-ref.mdx
@@ -97,7 +97,3 @@ package groups they include. The only allowed ways to refer to them are from the
the `package` function; they do not generate or consume files. For more
information, refer to the [`package_group`
documentation](/versions/8.2.1/reference/be/functions#package_group).
-
-
- Labelsarrow_forward
-
\ No newline at end of file
diff --git a/versions/8.2.1/concepts/dependencies.mdx b/versions/8.2.1/concepts/dependencies.mdx
index 9e326a7a..c74b28b1 100644
--- a/versions/8.2.1/concepts/dependencies.mdx
+++ b/versions/8.2.1/concepts/dependencies.mdx
@@ -352,21 +352,3 @@ filegroup(
```
You can then reference the label `my_data` as the data dependency in your test.
-
-
-
diff --git a/versions/8.2.1/concepts/labels.mdx b/versions/8.2.1/concepts/labels.mdx
index cc5e4da0..37724f9b 100644
--- a/versions/8.2.1/concepts/labels.mdx
+++ b/versions/8.2.1/concepts/labels.mdx
@@ -243,20 +243,3 @@ the build.
This directed acyclic graph over targets is called the _target graph_ or
_build dependency graph_, and is the domain over which the
[Bazel Query tool](/versions/8.2.1/query/guide) operates.
-
-
diff --git a/versions/8.2.1/remote/caching.mdx b/versions/8.2.1/remote/caching.mdx
index 90802fb5..949a1076 100644
--- a/versions/8.2.1/remote/caching.mdx
+++ b/versions/8.2.1/remote/caching.mdx
@@ -126,7 +126,7 @@ not provide technical support for bazel-remote.
This cache stores contents on disk and also provides garbage collection
to enforce an upper storage limit and clean unused artifacts. The cache is
-available as a [docker image] and its code is available on
+available as a [docker image](https://hub.docker.com/r/buchgr/bazel-remote-cache/) and its code is available on
[GitHub](https://github.com/buchgr/bazel-remote/).
Both the REST and gRPC remote cache APIs are supported.
diff --git a/versions/8.3.1/concepts/build-files.mdx b/versions/8.3.1/concepts/build-files.mdx
index 934730fb..0b4501f1 100644
--- a/versions/8.3.1/concepts/build-files.mdx
+++ b/versions/8.3.1/concepts/build-files.mdx
@@ -132,12 +132,3 @@ for anyone to create new rules.
programming language. Libraries can depend on other libraries,
and binaries and tests can depend on libraries, with the expected
separate-compilation behavior.
-
-
diff --git a/versions/8.3.1/concepts/build-ref.mdx b/versions/8.3.1/concepts/build-ref.mdx
index d14bae3d..2dac5555 100644
--- a/versions/8.3.1/concepts/build-ref.mdx
+++ b/versions/8.3.1/concepts/build-ref.mdx
@@ -97,7 +97,3 @@ package groups they include. The only allowed ways to refer to them are from the
the `package` function; they do not generate or consume files. For more
information, refer to the [`package_group`
documentation](/versions/8.3.1/reference/be/functions#package_group).
-
-
- Labelsarrow_forward
-
\ No newline at end of file
diff --git a/versions/8.3.1/concepts/dependencies.mdx b/versions/8.3.1/concepts/dependencies.mdx
index 19a142db..15af2848 100644
--- a/versions/8.3.1/concepts/dependencies.mdx
+++ b/versions/8.3.1/concepts/dependencies.mdx
@@ -349,13 +349,3 @@ filegroup(
```
You can then reference the label `my_data` as the data dependency in your test.
-
-
-
diff --git a/versions/8.3.1/concepts/labels.mdx b/versions/8.3.1/concepts/labels.mdx
index 69ba4335..b05be33c 100644
--- a/versions/8.3.1/concepts/labels.mdx
+++ b/versions/8.3.1/concepts/labels.mdx
@@ -239,12 +239,3 @@ the build.
This directed acyclic graph over targets is called the _target graph_ or
_build dependency graph_, and is the domain over which the
[Bazel Query tool](/versions/8.3.1/query/guide) operates.
-
-
diff --git a/versions/8.3.1/remote/caching.mdx b/versions/8.3.1/remote/caching.mdx
index 6141c102..c70ca277 100644
--- a/versions/8.3.1/remote/caching.mdx
+++ b/versions/8.3.1/remote/caching.mdx
@@ -126,7 +126,7 @@ not provide technical support for bazel-remote.
This cache stores contents on disk and also provides garbage collection
to enforce an upper storage limit and clean unused artifacts. The cache is
-available as a [docker image] and its code is available on
+available as a [docker image](https://hub.docker.com/r/buchgr/bazel-remote-cache/) and its code is available on
[GitHub](https://github.com/buchgr/bazel-remote/).
Both the REST and gRPC remote cache APIs are supported.
diff --git a/versions/8.4.2/concepts/build-files.mdx b/versions/8.4.2/concepts/build-files.mdx
index 2a8bec93..db47dddf 100644
--- a/versions/8.4.2/concepts/build-files.mdx
+++ b/versions/8.4.2/concepts/build-files.mdx
@@ -132,10 +132,3 @@ for anyone to create new rules.
programming language. Libraries can depend on other libraries,
and binaries and tests can depend on libraries, with the expected
separate-compilation behavior.
-
-
diff --git a/versions/8.4.2/concepts/build-ref.mdx b/versions/8.4.2/concepts/build-ref.mdx
index 4a1875b7..166fe41d 100644
--- a/versions/8.4.2/concepts/build-ref.mdx
+++ b/versions/8.4.2/concepts/build-ref.mdx
@@ -97,7 +97,3 @@ package groups they include. The only allowed ways to refer to them are from the
the `package` function; they do not generate or consume files. For more
information, refer to the [`package_group`
documentation](/versions/8.4.2/reference/be/functions#package_group).
-
-
- Labelsarrow_forward
-
\ No newline at end of file
diff --git a/versions/8.4.2/concepts/dependencies.mdx b/versions/8.4.2/concepts/dependencies.mdx
index de4279ff..11ebe5e6 100644
--- a/versions/8.4.2/concepts/dependencies.mdx
+++ b/versions/8.4.2/concepts/dependencies.mdx
@@ -332,11 +332,3 @@ filegroup(
```
You can then reference the label `my_data` as the data dependency in your test.
-
-
-
diff --git a/versions/8.4.2/concepts/labels.mdx b/versions/8.4.2/concepts/labels.mdx
index 72601041..34f013f7 100644
--- a/versions/8.4.2/concepts/labels.mdx
+++ b/versions/8.4.2/concepts/labels.mdx
@@ -239,10 +239,3 @@ the build.
This directed acyclic graph over targets is called the _target graph_ or
_build dependency graph_, and is the domain over which the
[Bazel Query tool](/versions/8.4.2/query/guide) operates.
-
-
diff --git a/versions/8.4.2/remote/caching.mdx b/versions/8.4.2/remote/caching.mdx
index 5b85e31d..af033d06 100644
--- a/versions/8.4.2/remote/caching.mdx
+++ b/versions/8.4.2/remote/caching.mdx
@@ -126,7 +126,7 @@ not provide technical support for bazel-remote.
This cache stores contents on disk and also provides garbage collection
to enforce an upper storage limit and clean unused artifacts. The cache is
-available as a [docker image] and its code is available on
+available as a [docker image](https://hub.docker.com/r/buchgr/bazel-remote-cache/) and its code is available on
[GitHub](https://github.com/buchgr/bazel-remote/).
Both the REST and gRPC remote cache APIs are supported.
diff --git a/versions/8.5.1/concepts/build-files.mdx b/versions/8.5.1/concepts/build-files.mdx
index 303cfc71..6a9c6680 100644
--- a/versions/8.5.1/concepts/build-files.mdx
+++ b/versions/8.5.1/concepts/build-files.mdx
@@ -132,14 +132,3 @@ for anyone to create new rules.
programming language. Libraries can depend on other libraries,
and binaries and tests can depend on libraries, with the expected
separate-compilation behavior.
-
-
diff --git a/versions/8.5.1/concepts/build-ref.mdx b/versions/8.5.1/concepts/build-ref.mdx
index 756f5fe1..2301173e 100644
--- a/versions/8.5.1/concepts/build-ref.mdx
+++ b/versions/8.5.1/concepts/build-ref.mdx
@@ -97,7 +97,3 @@ package groups they include. The only allowed ways to refer to them are from the
the `package` function; they do not generate or consume files. For more
information, refer to the [`package_group`
documentation](/versions/8.5.1/reference/be/functions#package_group).
-
-
- Labelsarrow_forward
-
\ No newline at end of file
diff --git a/versions/8.5.1/concepts/dependencies.mdx b/versions/8.5.1/concepts/dependencies.mdx
index 2a46e91f..4220df4b 100644
--- a/versions/8.5.1/concepts/dependencies.mdx
+++ b/versions/8.5.1/concepts/dependencies.mdx
@@ -352,21 +352,3 @@ filegroup(
```
You can then reference the label `my_data` as the data dependency in your test.
-
-
-
diff --git a/versions/8.5.1/concepts/labels.mdx b/versions/8.5.1/concepts/labels.mdx
index 5f6bff90..a9a0439d 100644
--- a/versions/8.5.1/concepts/labels.mdx
+++ b/versions/8.5.1/concepts/labels.mdx
@@ -239,14 +239,3 @@ the build.
This directed acyclic graph over targets is called the _target graph_ or
_build dependency graph_, and is the domain over which the
[Bazel Query tool](/versions/8.5.1/query/guide) operates.
-
-
diff --git a/versions/8.5.1/remote/caching.mdx b/versions/8.5.1/remote/caching.mdx
index 3a300a85..0a5ed506 100644
--- a/versions/8.5.1/remote/caching.mdx
+++ b/versions/8.5.1/remote/caching.mdx
@@ -126,7 +126,7 @@ not provide technical support for bazel-remote.
This cache stores contents on disk and also provides garbage collection
to enforce an upper storage limit and clean unused artifacts. The cache is
-available as a [docker image] and its code is available on
+available as a [docker image](https://hub.docker.com/r/buchgr/bazel-remote-cache/) and its code is available on
[GitHub](https://github.com/buchgr/bazel-remote/).
Both the REST and gRPC remote cache APIs are supported.
diff --git a/versions/8.6.0/concepts/build-files.mdx b/versions/8.6.0/concepts/build-files.mdx
index 08b5904a..09f8ae87 100644
--- a/versions/8.6.0/concepts/build-files.mdx
+++ b/versions/8.6.0/concepts/build-files.mdx
@@ -132,18 +132,3 @@ for anyone to create new rules.
programming language. Libraries can depend on other libraries,
and binaries and tests can depend on libraries, with the expected
separate-compilation behavior.
-
-
diff --git a/versions/8.6.0/concepts/build-ref.mdx b/versions/8.6.0/concepts/build-ref.mdx
index 3bdee30b..128daa84 100644
--- a/versions/8.6.0/concepts/build-ref.mdx
+++ b/versions/8.6.0/concepts/build-ref.mdx
@@ -97,7 +97,3 @@ package groups they include. The only allowed ways to refer to them are from the
the `package` function; they do not generate or consume files. For more
information, refer to the [`package_group`
documentation](/versions/8.6.0/reference/be/functions#package_group).
-
-
- Labelsarrow_forward
-
\ No newline at end of file
diff --git a/versions/8.6.0/concepts/dependencies.mdx b/versions/8.6.0/concepts/dependencies.mdx
index b1d14626..adc54f0d 100644
--- a/versions/8.6.0/concepts/dependencies.mdx
+++ b/versions/8.6.0/concepts/dependencies.mdx
@@ -366,19 +366,3 @@ filegroup(
```
You can then reference the label `my_data` as the data dependency in your test.
-
-
-
diff --git a/versions/8.6.0/concepts/labels.mdx b/versions/8.6.0/concepts/labels.mdx
index 87dfe0cd..d9d7b320 100644
--- a/versions/8.6.0/concepts/labels.mdx
+++ b/versions/8.6.0/concepts/labels.mdx
@@ -239,18 +239,3 @@ the build.
This directed acyclic graph over targets is called the _target graph_ or
_build dependency graph_, and is the domain over which the
[Bazel Query tool](/versions/8.6.0/query/guide) operates.
-
-
diff --git a/versions/8.6.0/remote/caching.mdx b/versions/8.6.0/remote/caching.mdx
index 9f744a2d..1317c1b7 100644
--- a/versions/8.6.0/remote/caching.mdx
+++ b/versions/8.6.0/remote/caching.mdx
@@ -126,7 +126,7 @@ not provide technical support for bazel-remote.
This cache stores contents on disk and also provides garbage collection
to enforce an upper storage limit and clean unused artifacts. The cache is
-available as a [docker image] and its code is available on
+available as a [docker image](https://hub.docker.com/r/buchgr/bazel-remote-cache/) and its code is available on
[GitHub](https://github.com/buchgr/bazel-remote/).
Both the REST and gRPC remote cache APIs are supported.
diff --git a/versions/9.0.0/concepts/build-files.mdx b/versions/9.0.0/concepts/build-files.mdx
index 42e7b901..164a1b78 100644
--- a/versions/9.0.0/concepts/build-files.mdx
+++ b/versions/9.0.0/concepts/build-files.mdx
@@ -130,13 +130,6 @@ for anyone to create new rules.
and binaries and tests can depend on libraries, with the expected
separate-compilation behavior.
-
-
## File encoding
`BUILD` and `.bzl` files should be encoded in UTF-8, of which ASCII is a valid
diff --git a/versions/9.0.0/concepts/build-ref.mdx b/versions/9.0.0/concepts/build-ref.mdx
index 6c0f7d78..df9ae0e8 100644
--- a/versions/9.0.0/concepts/build-ref.mdx
+++ b/versions/9.0.0/concepts/build-ref.mdx
@@ -97,7 +97,3 @@ package groups they include. The only allowed ways to refer to them are from the
the `package` function; they do not generate or consume files. For more
information, refer to the [`package_group`
documentation](/versions/9.0.0/reference/be/functions#package_group).
-
-
- Labelsarrow_forward
-
\ No newline at end of file
diff --git a/versions/9.0.0/concepts/dependencies.mdx b/versions/9.0.0/concepts/dependencies.mdx
index 218b243c..169b0f81 100644
--- a/versions/9.0.0/concepts/dependencies.mdx
+++ b/versions/9.0.0/concepts/dependencies.mdx
@@ -352,11 +352,3 @@ filegroup(
```
You can then reference the label `my_data` as the data dependency in your test.
-
-
-
diff --git a/versions/9.0.0/concepts/labels.mdx b/versions/9.0.0/concepts/labels.mdx
index 38059f37..fbd95b70 100644
--- a/versions/9.0.0/concepts/labels.mdx
+++ b/versions/9.0.0/concepts/labels.mdx
@@ -238,10 +238,3 @@ the build.
This directed acyclic graph over targets is called the _target graph_ or
_build dependency graph_, and is the domain over which the
[Bazel Query tool](/versions/9.0.0/query/guide) operates.
-
-
diff --git a/versions/9.0.0/remote/caching.mdx b/versions/9.0.0/remote/caching.mdx
index 78784ed6..0e5605fb 100644
--- a/versions/9.0.0/remote/caching.mdx
+++ b/versions/9.0.0/remote/caching.mdx
@@ -126,7 +126,7 @@ not provide technical support for bazel-remote.
This cache stores contents on disk and also provides garbage collection
to enforce an upper storage limit and clean unused artifacts. The cache is
-available as a [docker image] and its code is available on
+available as a [docker image](https://hub.docker.com/r/buchgr/bazel-remote-cache/) and its code is available on
[GitHub](https://github.com/buchgr/bazel-remote/).
Both the REST and gRPC remote cache APIs are supported.