OpenHarmony/third_party_mesa3d
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: fix a bunch of typos

Browse Source 
Saw a couple myself, and a quick round of vimspell showed a bunch more.

Signed-off-by: Eric Engestrom <eric@engestrom.ch>
Reviewed-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>
Reviewed-by: Erik Faye-Lund <erik.faye-lund@collabora.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5814>
This commit is contained in:
Eric Engestrom
2020-07-09 00:52:27 +02:00
committed by Marge Bot
parent 49d35f3d88
commit 9497a1fbe7
6 changed files with 12 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/ci/bare-metal.rst
View File

@@ -103,7 +103,7 @@ into that pool.
We need privileged mode and the /dev bind mount in order to get at the
serial console and fastboot USB devices (--device arguments don't
apply to devices that show up after container start, which is the case
with fastboot, and the servo serial devices are acctually links to
with fastboot, and the servo serial devices are actually links to
/dev/pts). We use host network mode so that we can (in the future)
spin up a server to collect XML results for fastboot.

2
docs/ci/docker.rst
View File

@@ -36,7 +36,7 @@ DUT requirements
----------------
In addition to the general :ref:`CI-farm-expectations`, using
docker requiers:
docker requires:
* DUTs must have a stable kernel and GPU reset (if applicable).

4
docs/ci/index.rst
View File

@@ -117,7 +117,7 @@ no ``parallel`` field set and:
to just run 1/10th of the test list.
If a HW CI farm goes offline (network dies and all CI pipelines end up
stalled) or its runners are consistenly spuriously failing (disk
stalled) or its runners are consistently spuriously failing (disk
full?), and the maintainer is not immediately available to fix the
issue, please push through an MR disabling that farm's jobs by adding
'.' to the front of the jobs names until the maintainer can bring
@@ -150,7 +150,7 @@ instead of silently reusing their container)
When developing a given change to your docker image, you would have to
bump the tag on each ``git commit --amend`` to your development
branch, which can get tedious. Instad, you can navigate to the
branch, which can get tedious. Instead, you can navigate to the
`container registry
<https://gitlab.freedesktop.org/mesa/mesa/container_registry>`_ for
your repository and delete the tag to force a rebuild. When your code