docs: Add reference documentation content to older versions

6.5.0/community/roadmaps-build-api.mdx

@@ -1,4 +1,4 @@
-<style>
+{/*
   .padbottom { padding-bottom: 10px; }
   .etabox {
     background: #EFEFEF;
@@ -24,7 +24,7 @@
     font-weight: bold;
     padding-left: 10px;
   }
-</style>
+*/}
 ---
 title: 'Bazel Build API 2021 Roadmap'
 ---

6.5.0/external/advanced.mdx

@@ -43,7 +43,7 @@ http_archive(
 )
 ```
 
-B/WORKSPACE {# This is not a buganizer link okay?? #}
+B/WORKSPACE {/* This is not a buganizer link okay?? */}
 
 ```python
 workspace(name = "B")

6.5.0/query/cquery.mdx

@@ -15,7 +15,7 @@ Bazel's loading phase, before options are evaluated.
 For example:
 
 ```
-$ cat > tree/BUILD <<EOF
+$ cat > tree/BUILD <<EOF
 sh_library(
     name = "ash",
     deps = select({
@@ -208,7 +208,7 @@ genrule(
      name = "my_gen",
      srcs = ["x.in"],
      outs = ["x.cc"],
-     cmd = "$(locations :tool) $&lt; >$@",
+     cmd = "$(locations :tool) $< >$@",
      tools = [":tool"],
 )
 cc_library(
@@ -533,7 +533,7 @@ different niches. Consider the following to decide which is right for you:
     that `query` avoids. For example,
     if `"//foo"` exists in two configurations, which one
     should `cquery "deps(//foo)"` use?
-    The `[config](#config)`</code> function can help with this.
+    The `[config](#config)` function can help with this.
 *   As a newer tool, `cquery` lacks support for certain use
     cases. See [Known issues](#known-issues) for details.
 
@@ -582,12 +582,12 @@ its `tools` attribute - that is, it configures its tools in the
 You can see the lingering effects of that transition below.
 
 ```
-$ cat > foo/BUILD &lt;&lt;&lt;EOF
+$ cat > foo/BUILD <<<EOF
 genrule(
     name = "my_gen",
     srcs = ["x.in"],
     outs = ["x.cc"],
-    cmd = "$(locations :tool) $&lt; >$@",
+    cmd = "$(locations :tool) $< >$@",
     tools = [":tool"],
 )
 cc_library(
@@ -608,7 +608,7 @@ tool(host_config)
 ```
 
 Workaround: change any startup option to force re-analysis of configured targets.
-For example, add `--test_arg=&lt;whatever&gt;` to your build command.
+For example, add `--test_arg=<whatever>` to your build command.
 
 ## Troubleshooting
 
@@ -638,7 +638,7 @@ constituent packages with a pre-processing query:
 
 ```
 # Replace "//foo/..." with a subshell query call (not cquery!) outputting each package, piped into
-# a sed call converting "&lt;pkg&gt;" to "//&lt;pkg&gt;:*", piped into a "+"-delimited line merge.
+# a sed call converting "<pkg>" to "//<pkg>:*", piped into a "+"-delimited line merge.
 # Output looks like "//foo:*+//foo/bar:*+//foo/baz".
 #
 $  bazel cquery --universe_scope=//foo:app "somepath(//foo:app, $(bazel query //foo/...