finn pushed to branch juerg/typos at BuildGrid / buildgrid
Commits:
3 changed files:
Changes:
... | ... | @@ -98,7 +98,7 @@ has ``gcc`` installed, run: |
98 | 98 |
|
99 | 99 |
The ``--remote`` option is used to specify the server location (running on the
|
100 | 100 |
same machine here, and listening to port 50051). The ``--parent`` option is used
|
101 |
-to specify the server instance you except the bot to be attached to. Refer to
|
|
101 |
+to specify the server instance you expect the bot to be attached to. Refer to
|
|
102 | 102 |
the :ref:`CLI reference section <invoking-bgd-bot-temp-directory>` for command
|
103 | 103 |
line interface details.
|
104 | 104 |
|
... | ... | @@ -120,7 +120,7 @@ You can finally have Bazel to build the example workspace by running: |
120 | 120 |
|
121 | 121 |
bazel build //main:hello-world
|
122 | 122 |
|
123 |
-You can verify that the example has been successfully build by running the
|
|
123 |
+You can verify that the example has been successfully built by running the
|
|
124 | 124 |
generated executable. Simply invoke:
|
125 | 125 |
|
126 | 126 |
.. code-block:: sh
|
... | ... | @@ -149,7 +149,7 @@ that the ``buildbox`` tool is functional on your machine (refer to |
149 | 149 |
|
150 | 150 |
The ``--remote`` option is used to specify the server location (running on the
|
151 | 151 |
same machine here, and listening to port 50051). The ``--parent`` option is
|
152 |
-used to specify the server instance you except the bot to be attached to (empty
|
|
152 |
+used to specify the server instance you expect the bot to be attached to (empty
|
|
153 | 153 |
here). ``--fuse-dir`` and ``--local-cas`` are specific to the ``buildbox`` bot
|
154 | 154 |
and respectively specify the sandbox mount point and local CAS cache locations.
|
155 | 155 |
Refer to the :ref:`CLI reference section <invoking-bgd-bot-buildbox>` for
|
... | ... | @@ -178,7 +178,7 @@ You can finally have BuildStream to build the example project by running: |
178 | 178 |
|
179 | 179 |
bst build hello.bst
|
180 | 180 |
|
181 |
-You can verify that the example has been successfully build by running the
|
|
181 |
+You can verify that the example has been successfully built by running the
|
|
182 | 182 |
generated executable. Simply invoke:
|
183 | 183 |
|
184 | 184 |
.. code-block:: sh
|
... | ... | @@ -97,7 +97,8 @@ tests_require = [ |
97 | 97 |
]
|
98 | 98 |
|
99 | 99 |
docs_require = [
|
100 |
- 'sphinx',
|
|
100 |
+ # rtd-theme broken in Sphinx >= 1.8, this breaks search functionality.
|
|
101 |
+ 'sphinx == 1.7.8',
|
|
101 | 102 |
'sphinx-click',
|
102 | 103 |
'sphinx-rtd-theme',
|
103 | 104 |
'sphinxcontrib-apidoc',
|