MozReview: Fix documentation display for hacking commands (Bug 1263960). r?mcote draft
authorDavid Walsh <>
Tue, 12 Apr 2016 10:43:44 -0500
changeset 7725 8e053da43d67cd501b9a48f9970698e79ea5b515
parent 7724 26ab2d5f91f8e493c76fb7efac30bfe9d630135d
child 7726 a7dd8bd9ef45e22bd81c53ec93737046cde2fa65
push id738
push dateTue, 12 Apr 2016 15:54:27 +0000
MozReview: Fix documentation display for hacking commands (Bug 1263960). r?mcote MozReview-Commit-ID: AjRyPmTRjkW
--- a/docs/hacking-mozreview.rst
+++ b/docs/hacking-mozreview.rst
@@ -34,37 +34,37 @@ Review Board Mercurial Extension
 Running a MozReview Instance
 It is possible to run a fully isolated, fully local MozReview instance
 from your machine. This will give you an environment that should behave
 like production.
 You will need Docker installed. On Linux, this is generally as simple
-as installing the required package, e.g., on Ubuntu,
+as installing the required package, e.g., on Ubuntu::
   $ sudo apt-get install
 You can also install the very latest release `directly from Docker <>`_.
 On Linux, it is necessary to configure Docker to listen on a tcp socket
 rather than the default configuration, which uses an unix domain socket,
 in order to get test results which match the expected results. This can be
 done by editing your configuration file to start docker with the following
   -H tcp://
 For OS X, you will need to install and start up docker-machine; see
 the official `installation instructions
 <>`_.  Make sure you specify
 more than the default 1024 MB of RAM, which is insufficient for a
 local MozReview installation, given the number of containers that are
 created.  If you're using VirtualBox as your driver, this should work
-(creating a docker machine called "default"):
+(creating a docker machine called "default")::
   docker-machine create --driver virtualbox --virtualbox-memory 4096 default
 Running a local MozReview instance in Windows is not yet supported,
 but if you get it working, please :ref:`let us know! <mozreview_getting_in_touch>`
 After you have docker up and running, you'll need to configure your
 environment. Run the following::