From d74b207e39ed9b6ae59116919af65de597b2ee19 Mon Sep 17 00:00:00 2001
From: Guillaume Gomez <contact@guillaume-gomez.fr>
Date: Sun, 26 Apr 2026 17:55:45 +0200
Subject: [PATCH] Fix indent of docs.rs build page code example

---
 .../templates/core/about/builds.html          | 20 +++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/crates/bin/docs_rs_web/templates/core/about/builds.html b/crates/bin/docs_rs_web/templates/core/about/builds.html
index 3c921132c..9080f57b0 100644
--- a/crates/bin/docs_rs_web/templates/core/about/builds.html
+++ b/crates/bin/docs_rs_web/templates/core/about/builds.html
@@ -32,19 +32,19 @@ <h4 id="setting-a-readme"> <a href="#setting-a-readme">Setting a README</a> </h4
             <h4 id="detecting-docsrs"> <a href="#detecting-docsrs">Detecting Docs.rs</a> </h4>
             <p>
                 To recognize Docs.rs from your Rust code, you can test for the <code>docsrs</code> cfg, e.g.:
-                {% filter dedent(None)|highlight("rust") -%}
-                    #[cfg(docsrs)]
-                    mod documentation;
+                {% filter highlight("rust") -%}
+#[cfg(docsrs)]
+mod documentation;
                 {%- endfilter %}
                 The `docsrs` cfg only applies to the final rustdoc invocation (i.e. the crate currently
                 being documented). It does not apply to dependencies (including workspace ones).
             </p>
             <p>
                 To recognize Docs.rs from <code>build.rs</code> files, you can test for the environment variable <code>DOCS_RS</code>, e.g.:
-                {% filter dedent(3)|highlight("rust") -%}
-                    if std::env::var("DOCS_RS").is_ok() {
-                        // ... your code here ...
-                    }
+                {% filter highlight("rust") -%}
+if std::env::var("DOCS_RS").is_ok() {
+    // ... your code here ...
+}
                 {%- endfilter %}
                 This approach can be helpful if you need dependencies for building the library, but not for building the documentation.
             </p>
@@ -56,9 +56,9 @@ <h4 id="cross-compiling"> <a href="#cross-compiling">Cross-compiling</a> </h4>
 
             <p>
                 You can configure how your crate is built by adding <a href="metadata">package metadata</a> to your <code>Cargo.toml</code>, e.g.:
-                {% filter dedent(None)|highlight("toml") -%}
-                    [package.metadata.docs.rs]
-                    rustc-args = ["--cfg", "my_cfg"]
+                {% filter highlight("toml") -%}
+[package.metadata.docs.rs]
+rustc-args = ["--cfg", "my_cfg"]
                 {%- endfilter %}
                 Here, the compiler arguments are set so that <code>#[cfg(my_cfg)]</code> (not to be confused with <code>#[cfg(doc)]</code>) can be used for conditional compilation.
                 This approach is also useful for setting <a href="https://doc.rust-lang.org/cargo/reference/features.html">cargo features</a>.