Misc docs cleanup and fixes (#155501)

dev/conductor/README.md

@@ -23,7 +23,7 @@ unlock your ssh key for the session; if you do not, each time the conductor
 attempts to interact with a remote, the user will be prompted to enter their ssh
 key password.
 
-** Confirm that your personal github clone of flutter/flutter is named flutter and flutter/engine is named engine. If not you will need to use flags to override the defaults.
+** Confirm that your personal GitHub clone of flutter/flutter is named flutter and flutter/engine is named engine. If not you will need to use flags to override the defaults.
 
 ## Usage
 

dev/conductor/RELEASE_ONBOARDING.md

@@ -2,61 +2,70 @@
 
 Googler facing documentation can be found at go/flutter-release-workflow.
 
-### Responsiblity
+### Responsibility
 
 Release engineer is responsible for:
-* Branch alignment and/or Sheparding cherry picks
+* Branch alignment and/or shepherding cherry picks
 * Decision making related to cherry pick risk
 * Verification that pre and post submits pass prior to publishing
 * Contributor facing communication
-* Some public facing post release comunication
+* Some public facing post release communication
 
 In the past (and possibly in the future) there was a distinction between a release engineer and release manager.
-For now the responsiblitys are the same and we will refer to the person managing the release as a release engineer.
+For now the responsibilities are the same and we will refer to the person managing the release as a release engineer.
 
 ## Onboarding
-One time setup instructions for new or returning relase engineers.
+
+One time setup instructions for new or returning release engineers.
 
 ### Groups/Permissions
 
-#### Join flutter-hackers on github
+#### Join flutter-hackers on GitHub
+
 https://github.com/orgs/flutter/teams/flutter-hackers/members
 
 #### [Googler only] Join mdb/flutter-infra
+
 Possibly not required
 https://ganpati2.corp.google.com/propose_membership?parent=9147533327&child=$me.prod
 
 #### Join the flutter-announce google group
+
 Ping any current release engineer to add you as an owner and give you publish access.
 https://groups.google.com/g/flutter-announce/members?q=role:owner&pli=1
 
 TODO include screenshot
 
 #### [Googler only] Install tool-proxy-client
-From a glinux machine run
-`sudo apt install tool-proxy-client`
+
+From a glinux machine run `sudo apt install tool-proxy-client`.
 
 `tool-proxy-client` is the tool that enables/enforces 2 party authorization for controlled builds.
 
 #### [Googler only] Confirm access to release calendar
+
 Public and Beta releases and timelines
 go/dash-team-releases
 
 #### [Googler only] Join release chatroom
+
 Release hotline https://chat.google.com/room/AAAA6RKcK2k?cls=7
 
 #### [Googler only] join mdb/flutter-release-team
+
 Controls who can approve 2 party auth requests.
 https://ganpati2.corp.google.com/propose_membership?parent=100213927583&child=$me.prod
 
 #### Setup conductor
+
 Conductor is a dart command line interface for common release tasks.
 Its instructions are in README.md.
 
-
 #### [Googler only] Confirm access to Apple signing cert update doc
+
 go/flutter-signing-apple-contracts
 Also confirm access to valentine entries listed in that doc.
 
 #### [Googler only] Access release engineer doc
+
 Confirm access to go/release-eng-retros

dev/devicelab/README.md

@@ -28,7 +28,7 @@ DeviceLab tests are run against physical devices in Flutter's lab (the
 
 Tasks specify the type of device they are to run on (`linux_android`, `mac_ios`,
 `mac_android`, `windows_android`, etc). When a device in the lab is free, it
-will pickup tasks that need to be completed.
+will pick up tasks that need to be completed.
 
 1. If the task succeeds, the test runner reports the success and uploads its
 performance metrics to Flutter's infrastructure. Not all tasks record