Minor grammar/punctuation/phrasing fixes.

Co-authored-by: C.A.M. Gerlach <CAM.Gerlach@Gerlach.CAM>
python · ezio-melotti · Mar 16, 2023 · Aug 6, 2022 · Dec 25, 2022 · Dec 25, 2022
commit ff2d0ee9a763822e43c3afaead21f00d372cbf0b
diff --git a/triage/labels.rst b/triage/labels.rst
@@ -100,7 +100,7 @@ Other labels
 * :gh-label:`triaged`: for issue has been accepted as valid by a triager.
 * :gh-label:`easy`: for issues that are considered easy.
 * :gh-label:`build`/:gh-label:`performance`: for issues related
-  to the build process or performances, respectively.
+  to the build process or performance, respectively.
 * :gh-label:`release-blocker`/:gh-label:`deferred-blocker`: for issues/PRs
   that, unless fixed, will hold the current or next release respectively.
   Triagers may set these labels for issues that must be fixed before a release,

diff --git a/triage/triaging.rst b/triage/triaging.rst
@@ -31,8 +31,8 @@ This field indicates who is expected to take the next step in resolving
 the issue.
 
 It is acceptable to assign an issue to someone if the issue cannot move
-forward without their help, e.g., they need to make a technical decision to
-allow the issue to move forward. Also consult the :ref:`experts` as certain
+forward without their help; e.g., they need to make a technical decision on
+how to proceed. Also consult the :ref:`experts` as certain
 stdlib modules should always be assigned to a specific person.
 
 Note that in order to assign an issue to someone, that person **must** be