fix a link

content/gsoc-final.md

@@ -41,7 +41,7 @@ At this point, the initial core configuration was ready, so I added a section to
 
 Here in the project, there was kind of a lull, and I was working on polishing tests and documentation.  However, one thing I was noticing was that it was kind of hard and involved to write a full integration test case.  My mentor suggested that I try to improve the testing infrastructure for `cargo-semver-checks`, and I thought that was a great idea.  In [#846](https://github.com/obi1kenobi/cargo-semver-checks/commit/329c42f1cfadba23454d881273f63df40a6291bc), I added the foundation to be able to write integration tests using the `insta` framework.  I also spent some time benchmarking to figure out what kind of test (i.e., `lib test`, `bin test`, or, confusingly, `test` binary) would be most helpful to access the right parts of `cargo-semver-checks` to test while having the fastest possible compile times for better iteration and design.  Here, I also wrote a lot of documentation for future contributors to have the best experience when writing new tests.
 
-After adding this test infrastructure, I wrote some tests that pinned down `cargo-semver-checks`'s behavior for different edge cases, which documented this behavior, prevented any unwanted regressions, and would be easy to change if we decided in the future we wanted this behavior to be different, in [#847](https://github.com/obi1kenobi/cargo-semver-checks/commit/0ed482776ba158df55ff3651aaa95019249e04b4), [#859](https://github.com/obi1kenobi/cargo-semver-checks/commit/c53ff88cd6d6d4e0631c4405d5f8c0da562d8218), [#866](https://github.com/obi1kenobi/cargo-semver-checks/commit/c53ff88cd6d6d4e0631c4405d5f8c0da562d8218), and [#882](https://github.com/obi1kenobi/cargo-semver-checks/commit/6e5d78acf899dbb232060cfc525b7444a3d2f7e5).  In writing these tests, I found the opportunity to polish in fix parts of the test infrastructure, like in [#865](https://github.com/obi1kenobi/cargo-semver-checks/commit/eb5c87dac9ce2c51d054272d6ba902cc4121bc3f), [#867](https://github.com/obi1kenobi/cargo-semver-checks/commit/8898271377a3931925ba38518b1995c96107795f), [#881](https://github.com/obi1kenobi/cargo-semver-checks/commit/5b35f9f3d66ea76a6dd87fa348fabd12224a30c3), and [#883](https://github.com/obi1kenobi/cargo-semver-checks/commit/c2dfe22505975f3092820e4464ccb2774e87928c), as well as [#913](https://github.com/obi1kenobi/cargo-semver-checks/commit/7b7a518150b7ff2701c40a61829896a2cd05898b) later on.
+After adding this test infrastructure, I wrote some tests that pinned down `cargo-semver-checks`'s behavior for different edge cases, which documented this behavior, prevented any unwanted regressions, and would be easy to change if we decided in the future we wanted this behavior to be different, in [#847](https://github.com/obi1kenobi/cargo-semver-checks/commit/0ed482776ba158df55ff3651aaa95019249e04b4), [#859](https://github.com/obi1kenobi/cargo-semver-checks/commit/62a3c75215399f9c5d853b7dad24147af6a01f42), [#866](https://github.com/obi1kenobi/cargo-semver-checks/commit/c53ff88cd6d6d4e0631c4405d5f8c0da562d8218), and [#882](https://github.com/obi1kenobi/cargo-semver-checks/commit/6e5d78acf899dbb232060cfc525b7444a3d2f7e5).  In writing these tests, I found the opportunity to polish in fix parts of the test infrastructure, like in [#865](https://github.com/obi1kenobi/cargo-semver-checks/commit/eb5c87dac9ce2c51d054272d6ba902cc4121bc3f), [#867](https://github.com/obi1kenobi/cargo-semver-checks/commit/8898271377a3931925ba38518b1995c96107795f), [#881](https://github.com/obi1kenobi/cargo-semver-checks/commit/5b35f9f3d66ea76a6dd87fa348fabd12224a30c3), and [#883](https://github.com/obi1kenobi/cargo-semver-checks/commit/c2dfe22505975f3092820e4464ccb2774e87928c), as well as [#913](https://github.com/obi1kenobi/cargo-semver-checks/commit/7b7a518150b7ff2701c40a61829896a2cd05898b) later on.
 
 ### new features!