[fixup] Review by McZen v2

Author: tingerrr

docs/process.md

@@ -114,7 +114,7 @@ At that point the RFC is "active" and may be implemented with the goal of eventu
   As a pull request the RFC will receive design feedback from the larger community, and the author should be prepared to revise it in response.
   The pull request should start with `RFC`/`Draft RFC` to clearly distinguish it from non-RFCs.
   The PR description should have a link to the markdown document so it can be viewed as a rendered page on your fork.
-  You can get do this by going to the file in the PR changes, clicking `View File` and replacing the commit hash with the branch name, this creates a link like so: `https://github.com/<your account>/<your fork>/blob/<your PR branch name>/<your RFC document path>`.
+  You can do this by going to the file in the PR changes, clicking `View File` and replacing the commit hash with the branch name, this creates a link like so: `https://github.com/<your account>/<your fork>/blob/<your PR branch name>/<your RFC document path>`.
 - Now that your RFC has an open pull request, use the issue number of the PR to rename the file: update your `0000-` prefix to that number.
   Also update the "RFC PR" link at the top of the file.
 - Each pull request will be labeled with the most relevant `T-*` labels, which aids in understanding the scope of an RFC.