diff --git a/docs/ci/bare-metal.rst b/docs/ci/bare-metal.rst
index 088c42cdc9e..af461d0b5e7 100644
--- a/docs/ci/bare-metal.rst
+++ b/docs/ci/bare-metal.rst
@@ -31,7 +31,7 @@ DRM functionality, or to fix kernel bugs.
 The boards must have networking, so that we can extract the dEQP .xml results to
 artifacts on GitLab, and so that we can download traces (too large for an
 initramfs) for trace replay testing.  Given that we need networking already, and
-our dEQP/piglit/etc. payload is large, we use nfs from the x86 runner system
+our dEQP/Piglit/etc. payload is large, we use nfs from the x86 runner system
 rather than initramfs.
 
 See `src/freedreno/ci/gitlab-ci.yml` for an example of fastboot on DB410c and
@@ -48,7 +48,7 @@ at /tftp in the container.
 
 Since we're going the TFTP route, we also use NFS root.  This avoids
 packing the rootfs and sending it to the board as a ramdisk, which
-means we can support larger rootfses (for piglit testing), at the cost
+means we can support larger rootfses (for Piglit testing), at the cost
 of needing more storage on the runner.
 
 Telling the board about where its TFTP and NFS should come from is
diff --git a/docs/ci/index.rst b/docs/ci/index.rst
index 522429073da..3bc6accffb4 100644
--- a/docs/ci/index.rst
+++ b/docs/ci/index.rst
@@ -142,7 +142,7 @@ able to handle a whole pipeline's worth of jobs in less than 15 minutes
 
 If a test farm is short the HW to provide these guarantees, consider dropping
 tests to reduce runtime.  dEQP job logs print the slowest tests at the end of
-the run, and piglit logs the runtime of tests in the results.json.bz2 in the
+the run, and Piglit logs the runtime of tests in the results.json.bz2 in the
 artifacts.  Or, you can add the following to your job to only run some fraction
 (in this case, 1/10th) of the dEQP tests.
 
diff --git a/docs/submittingpatches.rst b/docs/submittingpatches.rst
index 48886c78353..06483863f48 100644
--- a/docs/submittingpatches.rst
+++ b/docs/submittingpatches.rst
@@ -310,7 +310,7 @@ broad discretion in rejecting patches that have been nominated.
 -  It must not introduce a regression - be that build or runtime wise.
 
    .. note::
-      If the regression is due to faulty piglit/dEQP/CTS/other test
+      If the regression is due to faulty Piglit/dEQP/CTS/other test
       the latter must be fixed first. A reference to the offending test(s)
       and respective fix(es) should be provided in the nominated patch.