PEP 1: Correct minor issues in 'PEP Editor Responsibilities & Workflow'

Author: StanFromIreland

peps/pep-0001.rst

@@ -773,10 +773,10 @@ must watch the `PEP repository`_.
 
 Note that developers with write access to the `PEP repository`_ may
 handle the tasks that would normally be taken care of by the PEP editors.
-Alternately, even developers may request assistance from PEP editors by
+Alternatively, even developers may request assistance from PEP editors by
 mentioning ``@python/pep-editors`` on GitHub.
 
-For each new PEP that comes in an editor does the following:
+For each new PEP that comes in, an editor does the following:
 
 * Make sure that the PEP is either co-authored by a core developer, has a core
   developer as a sponsor, or has a sponsor specifically approved for this PEP
@@ -835,14 +835,14 @@ for changes, and correct any structure, grammar, spelling, or
 markup mistakes they see.
 
 PEP editors don't pass judgment on PEPs.  They merely do the
-administrative & editorial part (which is generally a low volume task).
+administrative and editorial part (which is generally a low volume task).
 
 Resources:
 
 * `Index of Python Enhancement Proposals <https://peps.python.org/>`_
 
 * `Following Python's Development
-  <https://devguide.python.org/communication/>`_
+  <https://devguide.python.org/developer-workflow/communication-channels/index.html>`_
 
 * `Python Developer's Guide <https://devguide.python.org/>`_