Skip to content

Commit e8526c2

Browse files
jeayetimabbott
authored andcommitted
Fix broken readme links, grammar, and formatting.
1 parent d3c32ab commit e8526c2

File tree

1 file changed

+7
-6
lines changed

1 file changed

+7
-6
lines changed

Diff for: README.md

+7-6
Original file line numberDiff line numberDiff line change
@@ -126,7 +126,7 @@ convention.
126126
discussion in the main [Zulip installation docs][install-normal]):
127127

128128
* `SETTINGS_EXTERNAL_HOST`: The hostname your users will use to
129-
connect to your Zulip server. If you're testing on your laptop, you
129+
connect to your Zulip server. If you're testing on your laptop,
130130
the default of `localhost.localdomain` is great.
131131
* `SETTINGS_ZULIP_ADMINISTRATOR`: The email address to receive error
132132
and support emails generated by the Zulip server and its users.
@@ -158,7 +158,7 @@ are secrets are set using the following syntax:
158158
`/etc/zulip/zulip-secrets.conf`.
159159

160160
Reading the comments in the sample
161-
[Zulip's settings.py file][prod-settings-template]) is the best way to
161+
[Zulip's settings.py file][prod-settings-template] is the best way to
162162
learn about the full set of Zulip's supported server-level settings.
163163

164164
Most settings in Zulip are just strings, but some are lists (etc.)
@@ -170,7 +170,7 @@ which you need to encode in the YAML file. For example,
170170

171171
**SSL Certificates**. By default, the image will generate a
172172
self-signed cert. We
173-
[will soon also support certbot](https://github.com/galexrt/docker-zulip/issues/120)
173+
[will soon also support certbot](https://github.com/zulip/docker-zulip/issues/120)
174174
for this, just like we do in normal Zulip installations
175175
(contributions welcome!).
176176

@@ -247,13 +247,14 @@ The following are helpful examples:
247247
# Get a (root) shell in the container so you can access logs
248248
docker-compose exec zulip /bin/bash
249249
# Create the initial Zulip organization
250-
docker-compose exec zulip sudo -H -u zulip -g zulip /home/zulip/deployments/current/manage.py generate_realm_creation_link
250+
docker-compose exec zulip sudo -H -u zulip -g zulip \
251+
/home/zulip/deployments/current/manage.py generate_realm_creation_link
251252
```
252253

253254
Since that process for running management commands is a pain, we recommend
254255
[using a wrapper script][wrapper-tool] for running management commands.
255256

256-
[wrapper-tool]: https://github.com/galexrt/docker-zulip/wiki/Running-Management-Commands
257+
[wrapper-tool]: https://github.com/zulip/docker-zulip/wiki/Running-Management-Commands
257258

258259
## Running a Zulip server with Kubernetes
259260

@@ -302,7 +303,7 @@ Zulip container behind an HTTP proxy.
302303
[This wiki page][proxy-wiki-page] documents how to do this correctly
303304
with `nginx`.
304305

305-
[proxy-wiki-page]: https://github.com/galexrt/docker-zulip/wiki/Proxying-via-nginx-on-host-machine
306+
[proxy-wiki-page]: https://github.com/zulip/docker-zulip/wiki/Proxying-via-nginx-on-host-machine
306307

307308
## Upgrading the Zulip container
308309

0 commit comments

Comments
 (0)