docs: Clean redundant relative links.

We previously had a convention of redundantly including the directory
in relative links to reduce mistakes when moving content from one file
to another.  However, these days we have a broken link checker in
test-documentation, and after #21237, MyST-Parser will check relative
links (including fragments) when you run build-docs.

Signed-off-by: Anders Kaseorg <anders@zulip.com>

docs/git/cheat-sheet.md

@@ -113,4 +113,4 @@ See also [fixing commits][fix-commit]
 
 [fix-commit]: fixing-commits.md
 [git-config-clone]: cloning.html#step-1b-clone-to-your-machine
-[git-overview]: ./overview.md
+[git-overview]: overview.md

docs/git/cloning.md

@@ -137,4 +137,4 @@ You can check the `Actions` tab of your repository to see the builds.
 [github-actions]: https://docs.github.com/en/actions
 [zulip-rtd-dev-first-time]: ../development/setup-vagrant.md
 [zulip-rtd-dev-overview]: ../development/overview.md
-[zulip-rtd-tools-setup]: ../git/zulip-tools.html#set-up-git-repo-script
+[zulip-rtd-tools-setup]: zulip-tools.html#set-up-git-repo-script

docs/git/collaborate.md

@@ -56,4 +56,4 @@ tools/fetch-pull-request <PR-number>
 ```
 
 [github-help-co-pr-locally]: https://help.github.com/en/articles/checking-out-pull-requests-locally
-[tools-pr]: ../git/zulip-tools.html#fetch-a-pull-request-and-rebase
+[tools-pr]: zulip-tools.html#fetch-a-pull-request-and-rebase

docs/git/overview.md

@@ -59,7 +59,7 @@ Git workflow, or if you'd like a Git refresher.
 [github-zulip]: https://github.com/zulip/
 [github-zulip-zulip]: https://github.com/zulip/zulip/
 [continuous-integration]: ../testing/continuous-integration.md
-[zulip-git-guide-fork-ci]: ../git/cloning.html#step-3-configure-continuous-integration-for-your-fork
+[zulip-git-guide-fork-ci]: cloning.html#step-3-configure-continuous-integration-for-your-fork
 [zulip-rtd-code-style]: ../contributing/code-style.md
 [zulip-rtd-commit-discipline]: ../contributing/version-control.html#commit-discipline
 [zulip-rtd-commit-messages]: ../contributing/version-control.html#commit-messages
@@ -67,5 +67,5 @@ Git workflow, or if you'd like a Git refresher.
 [zulip-rtd-lint-tools]: ../contributing/code-style.html#lint-tools
 [zulip-rtd-mypy]: ../testing/mypy.md
 [zulip-rtd-testing]: ../testing/testing.md
-[zulip-rtd-zulip-tools]: ../git/zulip-tools.md
+[zulip-rtd-zulip-tools]: zulip-tools.md
 [zulip-rtd-zulipbot-usage]: ../contributing/zulipbot-usage.md

docs/git/pull-requests.md

@@ -158,7 +158,7 @@ for another review.
 [github-help-about-pr]: https://help.github.com/en/articles/about-pull-requests
 [github-help-create-pr-fork]: https://help.github.com/en/articles/creating-a-pull-request-from-a-fork
 [images-create-pr]: ../images/zulip-open-pr.png
-[keep-up-to-date]: ../git/using.html#keep-your-fork-up-to-date
-[self-push-commits]: ../git/using.html#push-your-commits-to-github
+[keep-up-to-date]: using.html#keep-your-fork-up-to-date
+[self-push-commits]: using.html#push-your-commits-to-github
 [screenshots-gifs]: ../tutorials/screenshot-and-gif-software.md
 [wip-prs]: #work-in-progress-pull-requests

docs/git/troubleshooting.md

@@ -275,8 +275,8 @@ keep,** you'll need to use `git log FETCH_HEAD` to identify that hashes of the
 commits you want to keep and then `git cherry-pick <commit>` those commits into
 whichever branch you need to update.
 
-[clone-to-your-machine]: ../git/cloning.html#step-1b-clone-to-your-machine
-[connect-upstream]: ../git/cloning.html#step-1c-connect-your-fork-to-zulip-upstream
+[clone-to-your-machine]: cloning.html#step-1b-clone-to-your-machine
+[connect-upstream]: cloning.html#step-1c-connect-your-fork-to-zulip-upstream
 [gitbook-advanced-merging]: https://git-scm.com/book/en/v2/Git-Tools-Advanced-Merging#_advanced_merging
 [gitbook-basic-merge-conflicts]: https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging#Basic-Merge-Conflicts
 [gitbook-git-cherry-pick]: https://git-scm.com/docs/git-cherry-pick

docs/git/using.md

@@ -450,8 +450,8 @@ complicated rebase.
 [github-help-push]: https://help.github.com/en/articles/pushing-to-a-remote
 [github-help-rebase]: https://help.github.com/en/articles/using-git-rebase
 [github-help-sync-fork]: https://help.github.com/en/articles/syncing-a-fork
-[how-git-is-different]: ./the-git-difference.md
-[self-multiple-computers]: ../git/troubleshooting.html#working-from-multiple-computers
+[how-git-is-different]: the-git-difference.md
+[self-multiple-computers]: troubleshooting.html#working-from-multiple-computers
 [zulip-git-guide-up-to-date]: #keep-your-fork-up-to-date
 [zulip-rtd-commit-discipline]: ../contributing/version-control.html#commit-discipline
 [zulip-rtd-commit-messages]: ../contributing/version-control.html#commit-messages

docs/git/working-copies.md

@@ -7,7 +7,7 @@ repository that you are generally concerned with:
   repository](https://github.com/zulip/zulip) on GitHub. You probably
   don't have write access to this repository.
 - The **origin** remote: Your personal remote repository on GitHub.
-  You'll use this to share your code and create [pull requests](../git/pull-requests.md).
+  You'll use this to share your code and create [pull requests](pull-requests.md).
 - local copy: This lives on your laptop or your remote dev instance,
   and is what you'll use to make changes and create commits.
 
@@ -45,6 +45,6 @@ working copies:
 - `git remote`: This helps you configure short names for remotes.
 - `git pull`: This pulls code, but by default creates a merge commit
   (which you definitely don't want). However, if you've followed our
-  [cloning documentation](../git/cloning.md), this will do
+  [cloning documentation](cloning.md), this will do
   `git pull --rebase` instead, which is the only mode you'll want to
   use when working on Zulip.

docs/git/zulip-tools.md

@@ -176,5 +176,5 @@ git rebase --continue
 ```
 
 [github-zulip-zulip]: https://github.com/zulip/zulip/
-[zulip-git-guide-fetch-pr]: ../git/collaborate.html#check-out-a-pull-request-locally
-[zulip-git-guide-ci]: ../git/cloning.html#step-3-configure-continuous-integration-for-your-fork
+[zulip-git-guide-fetch-pr]: collaborate.html#check-out-a-pull-request-locally
+[zulip-git-guide-ci]: cloning.html#step-3-configure-continuous-integration-for-your-fork