paulmataruso/zulip
1
0
Fork 0
mirror of https://github.com/zulip/zulip.git synced 2025-11-03 13:33:24 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Fix broken anchor links in troubleshooting guide.

Browse Source 
Fixes #7056.
This commit is contained in:
Tim Abbott
2017-10-17 20:38:59 -07:00
parent c77c2f084c
commit fa71f64adb
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/dev-env-first-time-contributors.md
View File

@@ -16,12 +16,12 @@ Contents:
* [Step 2: Get Zulip code](#step-2-get-zulip-code)
* [Step 3: Start the development environment](#step-3-start-the-development-environment)
* [Step 4: Developing](#step-4-developing)
* [Troubleshooting & Common Errors](#troubleshooting-common-errors)
* [Troubleshooting & Common Errors](#troubleshooting--common-errors)
* [Specifying a proxy](#specifying-a-proxy)
**If you encounter errors installing the Zulip development
environment,** check
[Troubleshooting & Common Errors](#troubleshooting-common-errors). If
[Troubleshooting & Common Errors](#troubleshooting--common-errors). If
that doesn't help, please visit
[#provision help](https://chat.zulip.org/#narrow/stream/provision.20help)
in the [Zulip development community server](chat-zulip-org.html) for
@@ -330,7 +330,7 @@ provisioning if your Internet connection is unreliable. To retry, you
can use `vagrant provision` (`vagrant up` will just boot the guest
without provisioning after the first time). Other common issues are
documented in the
[Troubleshooting & Common Errors](#troubleshooting-common-errors)
[Troubleshooting & Common Errors](#troubleshooting--common-errors)
section. If that doesn't help, please visit
[#provision help](https://chat.zulip.org/#narrow/stream/provision.20help)
in the [Zulip development community server](chat-zulip-org.html) for
@@ -384,7 +384,7 @@ Congrats, you're now inside the Zulip development environment!
You can confirm this by looking at the command prompt, which starts
with `(zulip-py3-venv)vagrant@`. If it just starts with `vagrant@`, your
provisioning failed and you should look at the
[troubleshooting section](#troubleshooting-common-errors).
[troubleshooting section](#troubleshooting--common-errors).
Next, start the Zulip server: