docs: Fix formatting of warnings.

Fixes warning formatting in testing.md and setup-advanced.md
with reStructured Text so that the warnings stand out.
This commit is contained in:
David Rosa 2019-10-09 21:33:59 -07:00 committed by Tim Abbott
parent ed607bee2c
commit 3fb2339511
2 changed files with 11 additions and 7 deletions

View File

@ -24,9 +24,12 @@ If you are using a [remote server](../development/remote.md), see
the the
[section on creating appropriate user accounts](../development/remote.html#setting-up-user-accounts). [section on creating appropriate user accounts](../development/remote.html#setting-up-user-accounts).
**Warning**: there is no supported uninstallation process with this ```eval_rst
method. If you want that, use the Vagrant environment, where you can .. warning::
just do `vagrant destroy` to clean up the development environment. there is no supported uninstallation process with this
method. If you want that, use the Vagrant environment, where you can
just do `vagrant destroy` to clean up the development environment.
```
Start by [cloning your fork of the Zulip repository][zulip-rtd-git-cloning] Start by [cloning your fork of the Zulip repository][zulip-rtd-git-cloning]
and [connecting the Zulip upstream repository][zulip-rtd-git-connect]: and [connecting the Zulip upstream repository][zulip-rtd-git-connect]:

View File

@ -207,10 +207,11 @@ and then run `tools/do-destroy-rebuild-test-database`
### Recreating the postgres cluster ### Recreating the postgres cluster
> **warning** ```eval_rst
> .. warning::
> **This is irreversible, so do it with care, and never do this anywhere This is irreversible! Do it with care and never do this anywhere
> in production.** in production.
```
If your postgres cluster (collection of databases) gets totally trashed If your postgres cluster (collection of databases) gets totally trashed
permissions-wise, and you can't otherwise repair it, you can recreate permissions-wise, and you can't otherwise repair it, you can recreate