docs: Fix lint/whitespace errors in GCI docs.

docs/fixing-commits.md

@@ -1,5 +1,7 @@
 # Fixing Commits
-This is mostly from https://help.github.com/articles/changing-a-commit-message/#rewriting-the-most-recent-commit-message
+This is mostly from
+[here](https://help.github.com/articles/changing-a-commit-message/#rewriting-the-most-recent-commit-message).
+
 ## Fixing the last commit
 ### Changing the last commit message
 1. `git commit --amend -m "New Message"`

docs/working-copies.md

@@ -18,13 +18,13 @@ the various working copies.
 
 Sometimes you need to get commits.  Here are some scenarios:
 
-- You may fork the official Zulip repo to your Github fork.
+- You may fork the official Zulip repo to your GitHub fork.
 - You may fetch commits from the offical Zulip repo to your local copy.
 - You occasionally may fetch commits from your forked copy.
 
 Sometimes you want to publish commits.  Here are scenarios:
 
-- You push code from your local copy to your Github fork.  (You usually
+- You push code from your local copy to your GitHub fork.  (You usually
   want to put the commit on a feature branch.)
 - You submit a PR to the official Zulip repo.
 

tools/documentation_crawler/documentation_crawler/spiders/common/spiders.py

@@ -17,6 +17,8 @@ EXCLUDED_URLS = [
     'https://calendar.google.com/calendar/embed?src=ktiduof4eoh47lmgcl2qunnc0o@group.calendar.google.com',
     # Returns 409 errors to HEAD requests frequently
     'https://medium.freecodecamp.com',
+    # Returns 404 to HEAD requests unconditionally
+    'https://www.git-tower.com/blog/command-line-cheat-sheet/',
 ]