diff --git a/docs/src/developer.md b/docs/src/developer.md
index 4c411010b..900875a38 100644
--- a/docs/src/developer.md
+++ b/docs/src/developer.md
@@ -120,7 +120,7 @@ assembly routines. The unit tests source code is located in the
 [`test/unit/`](https://github.com/awslabs/palace/blob/main/test/unit/) directory, and can be
 built from within the *Palace* build directory using `make unit-tests`, or from the
 superbuild as `make palace-tests`. The unit tests can be accelerated using MPI and/or
-OpenMP parallelism(when configured with `PALACE_WITH_OPENMP=ON`), but in all cases they are
+OpenMP parallelism (when configured with `PALACE_WITH_OPENMP=ON`), but in all cases they are
 only testing the local operator assembly on each process. The 2D and 3D sample meshes in
 [`test/unit/mesh/`](https://github.com/awslabs/palace/blob/main/test/unit/mesh/) come from
 the [MFEM repository](https://github.com/mfem/mfem/tree/master/data).
diff --git a/docs/src/guide/parallelism.md b/docs/src/guide/parallelism.md
index c04f54b4f..caadcd3f2 100644
--- a/docs/src/guide/parallelism.md
+++ b/docs/src/guide/parallelism.md
@@ -20,7 +20,7 @@ Lastly, *Palace* supports GPU-acceleration using NVIDIA and AMD GPUs, activated
 build options `-DPALACE_WITH_CUDA=ON` and `-DPALACE_WITH_HIP=ON`, respectively. At runtime,
 the [`config["Solver"]["Device"]`](../config/solver.md#config%5B%22Solver%22%5D) parameter
 in the configuration file can be set to `"CPU"` (the default) or `"GPU"` in order to
-configure *Palace* and MFEM to use the available GPU(s). The
+configure *Palace* and MFEM to use the available GPU device or devices. The
 [`config["Solver"]["Backend"]`](../config/solver.md#config%5B%22Solver%22%5D) parameter, on
 the other hand, controls the
 [libCEED backend](https://libceed.org/en/latest/gettingstarted/#backends). Users typically
diff --git a/docs/src/guide/postprocessing.md b/docs/src/guide/postprocessing.md
index d172d4e42..24a6ed555 100644
--- a/docs/src/guide/postprocessing.md
+++ b/docs/src/guide/postprocessing.md
@@ -58,7 +58,7 @@ These include:
     (associated with the specified domain attributes and indexed by the specified integer
     `"Index"`). These are from the electric and magnetic field solutions and written to the
     same `domain-E.csv` file in the specified postprocessing output directory used for the
-    global energies(described above).
+    global energies (described above).
   - [`config["Domains"]["Postprocessing"]["Probe"]`](../config/domains.md#domains%5B%22Postprocessing%22%5D%5B%22Probe%22%5D) :
     Probe the values of the computed electric field and magnetic flux density solutions at
     specified locations in the computational domain. The availability of the ``\bm{E}`` and
diff --git a/docs/src/guide/problem.md b/docs/src/guide/problem.md
index 44f9f895c..6dfdff07e 100644
--- a/docs/src/guide/problem.md
+++ b/docs/src/guide/problem.md
@@ -62,7 +62,7 @@ type and stored in an ASCII file named `port-S.csv`, in the directory specified
 ``\text{dB}`` magnitude (``20\log_{10}(|S_{ij}|)``) and the phase ``\angle(S_{ij})``
 (in degrees) are written to the file. In the case that more than a single lumped or wave
 port is excited or surface current excitations are used, scattering parameter output will
-be disabled for the simulation(though other quantities of interest are still
+be disabled for the simulation (though other quantities of interest are still
 postprocessed). When lumped ports are present, the peak complex lumped port voltages and
 currents computed for each excitation frequency are written to ASCII files named
 `port-V.csv` and `port-I.csv`, respectively, Additionally, the surface current excitations
diff --git a/docs/src/reference.md b/docs/src/reference.md
index a5de2371a..a9ab9475a 100644
--- a/docs/src/reference.md
+++ b/docs/src/reference.md
@@ -298,7 +298,7 @@ where ``\bm{D}_m = \varepsilon_r\bm{E}_m`` is the electric flux density for mode
 the second term on the right-hand side accounts for any lumped capacitive boundaries with
 nonzero circuit capacitance ``C_j``.
 
-The EPR can also be used to estimate mode quality factors due to input-output(I-O) line
+The EPR can also be used to estimate mode quality factors due to input-output (I-O) line
 coupling. The mode coupling quality factor due to the ``j``-th I-O port is given by
 
 ```math