diff --git a/guide/src/web-sys/supporting-more-web-apis.md b/guide/src/web-sys/supporting-more-web-apis.md
index e1a2886e..6ea0f7dc 100644
--- a/guide/src/web-sys/supporting-more-web-apis.md
+++ b/guide/src/web-sys/supporting-more-web-apis.md
@@ -47,13 +47,13 @@
```
* If the new API is **not** showing up in the docs,
- rebuild the `web-sys` crate [with logging enabled](/web-sys/logging.html)
+ rebuild the `web-sys` crate [with logging enabled](web-sys/logging.html)
and look for warning messages that mention your new API. Figure out why
bindings weren't generated and then add support to `wasm_bindgen_webidl` for
whatever is needed to generate your API's bindings.
-
- > You might find it helpful to view the generated rust bindings, to see if
- they are what you would expect. The file will be located at
+
+ > You might find it helpful to view the generated rust bindings, to see if
+ they are what you would expect. The file will be located at
`target/wasm32-unknown-unknown/debug/build/web-sys-xxx/out/bindings.rs`,
where `xxx` is a combinations of numbers and letters that represents your
build. This file is pretty unintelligable until you run `rustfmt` on it, like
@@ -61,6 +61,6 @@
4. Add a simple test for your new API to
`crates/web-sys/tests/all/`. See the [`web-sys` testing
- documentation](/web-sys/testing.html) for details.
+ documentation](web-sys/testing.html) for details.
5. Send a pull request! 😊
diff --git a/guide/src/web-sys/testing.md b/guide/src/web-sys/testing.md
index fe4c529c..78cb862d 100644
--- a/guide/src/web-sys/testing.md
+++ b/guide/src/web-sys/testing.md
@@ -10,7 +10,7 @@ cargo test
These tests all use a headless Firefox browser. See the [*Headless Browser
Tests* section for details on setup and
-configuration.](../contributing.html#headless-browser-tests)
+configuration.](contributing.html#headless-browser-tests)
## Grouping Tests