diff --git a/doc/procps.3 b/doc/procps.3
index 749e8729..3798d3d6 100644
--- a/doc/procps.3
+++ b/doc/procps.3
@@ -145,7 +145,7 @@ For the \fBstat\fR interface, a \fIwhat\fR parameter on the \fBreap\fR
 function identifies whether data for just CPUs or both CPUs and NUMA
 nodes is to be gathered.
 
-When usng the \fBsort\fR function, the parameters \fIstacks\fR and
+When using the \fBsort\fR function, the parameters \fIstacks\fR and
 \fInumstacked\fR would normally be those returned in the `reaped'
 structure.
 
@@ -172,7 +172,7 @@ It assumes that a supplied macro in the header file is
 used to access the `result' value.
 
 This feature can be activated through either of the following
-methods and any discrepancies will be wrtten to \fBstderr\fR.
+methods and any discrepancies will be written to \fBstderr\fR.
 
 .IP 1) 3
 Add CFLAGS='-DXTRA_PROCPS_DEBUG' to any other ./configure
diff --git a/doc/procps_pids.3 b/doc/procps_pids.3
index 6f921d4e..3de5061a 100644
--- a/doc/procps_pids.3
+++ b/doc/procps_pids.3
@@ -142,7 +142,7 @@ The \fBselect\fR function requires an array of PIDs or UIDs as
 are to be fetched.
 This function then operates as a subset of \fBreap\fR.
 
-When usng the \fBsort\fR function, the parameters \fIstacks\fR and
+When using the \fBsort\fR function, the parameters \fIstacks\fR and
 \fInumstacked\fR would normally be those returned in the `pids_fetch'
 structure.
 
@@ -179,7 +179,7 @@ It assumes that a supplied macro in the header file is
 used to access the `result' value.
 
 This feature can be activated through either of the following
-methods and any discrepancies will be wrtten to \fBstderr\fR.
+methods and any discrepancies will be written to \fBstderr\fR.
 
 .IP 1) 3
 Add CFLAGS='-DXTRA_PROCPS_DEBUG' to any other ./configure