mirror of
https://github.com/zulip/zulip.git
synced 2025-10-23 04:52:12 +00:00
docs: Add comma to all uses of "e.g." in contributor docs.
This commit is contained in:
committed by
Tim Abbott
parent
2bb037f2a0
commit
62d452f983
@@ -132,7 +132,7 @@ installation method described here. We require version 0.67.6+ of WSL 2.
|
||||
$ sudo apt install rabbitmq-server memcached redis-server postgresql
|
||||
```
|
||||
|
||||
1. Open `/etc/rabbitmq/rabbitmq-env.conf` using e.g.:
|
||||
1. Open `/etc/rabbitmq/rabbitmq-env.conf` using e.g.,:
|
||||
|
||||
```console
|
||||
$ sudo nano /etc/rabbitmq/rabbitmq-env.conf
|
||||
@@ -955,7 +955,7 @@ The `vagrant up` command basically does the following:
|
||||
|
||||
To debug such errors, you can log in to the Vagrant guest machine by
|
||||
running `vagrant ssh`, which should present you with a standard shell
|
||||
prompt. You can debug interactively by using e.g.
|
||||
prompt. You can debug interactively by using e.g.,
|
||||
`cd zulip && ./tools/provision`, and then running the individual
|
||||
subcommands that failed. Once you've resolved the problem, you can
|
||||
rerun `tools/provision` to proceed; the provisioning system is
|
||||
@@ -1094,7 +1094,7 @@ NO_PROXY localhost,127.0.0.1,.example.com,.zulipdev.com
|
||||
```
|
||||
|
||||
For proxies that require authentication, the config will be a bit more
|
||||
complex, e.g.:
|
||||
complex, e.g.,:
|
||||
|
||||
```text
|
||||
HTTP_PROXY http://userName:userPassword@192.168.1.1:8080
|
||||
@@ -1119,7 +1119,7 @@ then do a `vagrant reload`.
|
||||
### Using a different port for Vagrant
|
||||
|
||||
You can also change the port on the host machine that Vagrant uses by
|
||||
adding to your `~/.zulip-vagrant-config` file. E.g. if you set:
|
||||
adding to your `~/.zulip-vagrant-config` file. E.g., if you set:
|
||||
|
||||
```text
|
||||
HOST_PORT 9971
|
||||
|
Reference in New Issue
Block a user