Apply suggestions from code review

Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>

Author: sethmlarson

developer-workflow/psrt.csv

@@ -8,14 +8,14 @@ Gregory P. Smith,gpshead,
 Hugo van Kemenade,hugovk,Release Manager
 Jacob Coffee,JacobCoffee,
 Larry Hastings,larryhastings,
-Łukasz Langa,ambv,
+Łukasz Langa,ambv,Release Manager
 Ned Deily,ned-deily,"Admin, Release Manager"
 Pablo Galindo Salgado,pablogsal,Release Manager
 Paul McMillan,paulmcmillan,
 Pradyun Gedam,pradyunsg,
 Savannah Bailey,savannahostrowski,Release Manager
 Seth Larson,sethmlarson,Admin
-Steve Dower,zooba,
+Steve Dower,zooba,Release Manager
 Serhiy Storchaka,serhiy-storchaka,
 Thomas Wouters,Yhg1s,Release Manager
 Tim Peters,tim-one,

developer-workflow/psrt.rst

@@ -43,13 +43,13 @@ Responsibilities of PSRT members
 Below are the responsibilities of PSRT members:
 
 * Being knowledgeable about typical software vulnerability report handling
-  processes, such as CVE IDs, patches, coordinated disclosure, embargoes, etc.
+  processes, such as CVE IDs, patches, coordinated disclosure, embargoes.
 * Not sharing or acting on embargoed information about the reported
   vulnerability. Examples of disallowed behavior include sharing information
   with colleagues or publicly deploying unpublished mitigations or patches ahead
   of the advisory publication date.
 * Acting as a “Coordinator” of vulnerability reports that are submitted to
-  projects. A coordinator’s responsibility is to move a report through the PSRT
+  projects. A Coordinator’s responsibility is to move a report through the PSRT
   process to a “finished” state, either rejected or as a published advisory and
   mitigation, within the industry standard timeline of 90 days.
 * As a Coordinator, involving relevant core team members or triagers where