From 9eeaf64443f72925a87fe0310a68a8f205464aa3 Mon Sep 17 00:00:00 2001
From: plinss <plinss@users.noreply.github.com>
Date: Mon, 3 Jun 2024 16:10:56 +0000
Subject: [PATCH] deploy: c3eaec9458eecba3f53dfe3f28be2f472cc92bef

---
 index.html | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/index.html b/index.html
index 1ccf7dd..859fa2a 100644
--- a/index.html
+++ b/index.html
@@ -7,7 +7,7 @@
   <link href="https://www.w3.org/StyleSheets/TR/2021/W3C-ED" rel="stylesheet">
   <meta content="Bikeshed version 4afc1fdf9, updated Tue May 28 15:43:17 2024 -0700" name="generator">
   <link href="https://www.w3.org/TR/design-principles/" rel="canonical">
-  <meta content="55a06e0c517a72147e4103b9fbb7b5cca012873b" name="revision">
+  <meta content="c3eaec9458eecba3f53dfe3f28be2f472cc92bef" name="revision">
   <meta content="dark light" name="color-scheme">
   <link href="https://www.w3.org/StyleSheets/TR/2021/dark.css" media="(prefers-color-scheme: dark)" rel="stylesheet" type="text/css">
 <style>
@@ -1121,7 +1121,11 @@ <h3 class="heading settled" data-level="1.7" id="new-features"><span class="secn
    <p>Before adding items, consider integration with existing, similar capabilities.
 If this leads to a preferred design approach that cannot be implemented by only adding items,
 it might still be possible; see <a href="#removing-features">§ 1.8 Remove or change capabilities only once you understand existing usage</a>.</p>
-   <p>Do not assume that a change or removal is impossible without first checking.</p>
+   <p>Do not assume that a change or removal is impossible without first checking.
+Before adding items, consider integration with existing, similar capabilities.
+If this leads to a preferred design approach that cannot be implemented by only adding items,
+it might still be possible; see <a href="#removing-features">§ 1.8 Remove or change capabilities only once you understand existing usage</a>.
+Do not assume that a change or removal is impossible without first checking.</p>
    <h3 class="heading settled" data-level="1.8" id="removing-features"><span class="secno">1.8. </span><span class="content">Remove or change capabilities only once you understand existing usage</span><a class="self-link" href="#removing-features"></a></h3>
    <p>Prioritize compatibility with existing content when removing or changing functionality.</p>
    <p>Once a significant amount of content has come to depend on a particular behavior,