Skip to content

Commit 9a66118

Browse files
alexmvtimabbott
authored andcommitted
README: Fix casing.
1 parent 3c068d5 commit 9a66118

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ To use `docker-zulip`, you need the following:
3737
you can get away with significantly less especially for the
3838
`postgres`, `memcached`, etc. containers, because Docker makes it
3939
easy to sharply limit the RAM allocated to the services Zulip
40-
depends on, like redis, memcached, and postgresql (at the cost of
40+
depends on, like Redis, memcached, and PostgreSQL (at the cost of
4141
potential performance issues).
4242
- This project doesn't support `docker-rootless`; Zulip needs root
4343
access to set properties like the maximum number of open file
@@ -135,11 +135,11 @@ character works.
135135
instance. `SECRETS_postgres_password` configures the Zulip server to
136136
know the PostgreSQL password. While `SECRETS_postgres_password` is
137137
synced to the Zulip container on every boot, `POSTGRES_PASSWORD` is
138-
only accessed by the postgres container on first boot, so if you
139-
later want to change your postgres password after booting the
138+
only accessed by the PostgreSQL container on first boot, so if you
139+
later want to change your PostgreSQL password after booting the
140140
container, you'll need to either do an [ALTER
141141
ROLE][postgres-alter-role] query inside the `postgres` container or
142-
rebuild the postgres database (only if you don't need your data!).
142+
rebuild the PostgreSQL database (only if you don't need your data!).
143143
- `RABBITMQ_DEFAULT_PASS` and `SECRETS_rabbitmq_password` are similar,
144144
just for the RabbitMQ container.
145145
- `MEMCACHED_PASSWORD` and `SECRETS_memcached_password` are similar,
@@ -318,7 +318,7 @@ The Zulip build process installs packages via `yarn` and `pip`, and
318318
these need packages to be configured to use your custom CA
319319
certificates. You will need to get your certificate bundle into the
320320
docker image, either by adding a `COPY` somewhere or by replacing the
321-
`FROM`s with a custom ubuntu image that includes your bundle. The
321+
`FROM`s with a custom Ubuntu image that includes your bundle. The
322322
recommended way is to have your own base image which has your bundle
323323
ready at the default `/etc/ssl/certs/ca-certificates.crt`.
324324

0 commit comments

Comments
 (0)