diff --git a/bin/build b/bin/build
index 42993d0..9946fe2 100755
--- a/bin/build
+++ b/bin/build
@@ -6,7 +6,7 @@ astro check && astro build
 if [ "$?" -ne "0" ]; then
 	exit 1
 fi
-./bin/check_links.sh
+./bin/check_links.sh | grep -v "#starlight-image-zoom-icon-zoom" | grep -v "^unused page /demo-explainer/"
 [ -n "$GS" ] && echo -n "google-site-verification: ${GS}" > ./dist/${GS}
 
 find dist -type f -exec grep -l 'script src="/chamber.js/"' {} \; | xargs sed -i 's|script src="/chamber.js/"|script src="/chamber.js"|'
diff --git a/src/content/docs/basics/examples.mdx b/src/content/docs/basics/examples.mdx
index 11e9b86..4468f13 100644
--- a/src/content/docs/basics/examples.mdx
+++ b/src/content/docs/basics/examples.mdx
@@ -7,9 +7,9 @@ import DemoLink from "src/components/DemoLink.astro";
 
 This page references a series of view transition examples, starting with basic configurations and progressively incorporating more features. The tables below provide a brief description of what distinguishes each example and includes a link to the live example which also includes its code and a detailed explanation.
 
-You should be familiar with the [default animations](/tips/default-animations/) inserted by the View Transition API.
+You should be familiar with the [default animations](/basics/default-animations/) inserted by the View Transition API.
 
-The [first set of examples](#same-document-view-transitiom-examples) focuses on **exit and entry** animations for **same-document** view-transitions, animating a component directly on its page.
+The [first set of examples](#same-document-view-transition-examples) focuses on **exit and entry** animations for **same-document** view-transitions, animating a component directly on its page.
 
 The [second set of examples](#cross-document-view-transition-examples) highlights **exit and entry** animations of **cross-document** view transitions. Those are triggered by following a link to a new page.
 
diff --git a/src/content/docs/tools/inspection-chamber/index.mdx b/src/content/docs/tools/inspection-chamber/index.mdx
index dd6083c..e5196a6 100644
--- a/src/content/docs/tools/inspection-chamber/index.mdx
+++ b/src/content/docs/tools/inspection-chamber/index.mdx
@@ -139,7 +139,7 @@ Hint: If selected, Tutorial mode prominently displays usage instructions!
 7. <b>End the current view transition:</b> In Bypass and Slow Motion modes, the view
    transition will play once and then end automatically. Full Control mode must be
    ended explicitly. To do this, either click the "Exit" button in the Full Control
-   panel, click on the [Play Indicator](#play-indicator), or select another inspection
+   panel, click on the [Play Indicator](#play-indicator-), or select another inspection
    mode.
 
 </Steps>
@@ -167,7 +167,7 @@ Here you got two sliders: The lower slider animates the initially empty set of s
 
 Use the [Name List](#name-list) to select one or more transition groups to be controlled by the lower slider. In Full Control mode, clicking a selected name unselects it. You can reset all names by pressing the reset button of the name list.
 
-To exit Full Control mode, click the exit button in the full control panel or click the [Play Indicator](#play-indicator) in the upper left corner of the page.
+To exit Full Control mode, click the exit button in the full control panel or click the [Play Indicator](#play-indicator-) in the upper left corner of the page.
 
 </div></div>
 
diff --git a/src/pages/demo-explainer/FailIM.mdx b/src/pages/demo-explainer/FailIM.mdx
index 277f9a4..f09044a 100644
--- a/src/pages/demo-explainer/FailIM.mdx
+++ b/src/pages/demo-explainer/FailIM.mdx
@@ -23,7 +23,7 @@ The HTML of this example is very simple:
 The view transition swaps the two DOMs, each containing a background div and an image.
 
 
-The key to understanding this example lies in the order in which the `::view-transition-group` pseudo-elements [are created](/basics/pseudos/#creation--of-pseudo-elements) by the API and [hide each other](/basics/pseudos/#rendering-of-pseudo-elements).
+The key to understanding this example lies in the order in which the `::view-transition-group` pseudo-elements [are created](/basics/pseudos/#creation--of-pseudo-elements) by the API and [hide each other](/basics/pseudos/#rendering-pseudo-elements).
 
 
 When snapshots of the new images are taken in the new DOM, the `::view-transition-new` pseudo-elements are added to existing transition groups based on their transition names. These groups either already exist if there is an old image with the same name or they are created created on the fly. Elements that only exist in the new DOM will create new groups at the end of the list. When rendered, these late additions may obscure other images.