{GitHub,Gerrit}Access, Gomote: make access request more consistent

Remove the suggestion to include "CC @golang/release" because it
silently has no effect if the GitHub account posting it does not
already have some access within the 'golang' GitHub organization.
We'll instead rely on issue triage (and gopherbot) to find these.

Also be more specific that a new issue is expected to be made.
In some cases where a person has previously applied and their
request wasn't accepted, they may opt to re-open the previous
issue. A small tweak for now since this happens fairly rarely.

Change-Id: I14f1f46f1eece1e4ba9f25c9d2d9e4d0f0d832e8
Reviewed-on: https://go-review.googlesource.com/c/wiki/+/578495
Reviewed-by: Carlos Amedee <carlos@golang.org>
Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org>
diff --git a/GerritAccess.md b/GerritAccess.md
index b3a1254..ef0bcb1 100644
--- a/GerritAccess.md
+++ b/GerritAccess.md
@@ -62,7 +62,7 @@
 
 # Requesting Access
 
-To get request any of the access types above, file a bug (https://github.com/golang/go/issues/new?title=access:+&body=See+https://go.dev/wiki/GerritAccess) and list and state which access you want, and state the Google account you use to log in to Gerrit.
+To request any of the access types above, file a new issue (https://go.dev/issue/new?title=access:+&body=See+https://go.dev/wiki/GerritAccess.) and state which access you want, and state the Google account you use to log in to Gerrit.
 
 Decisions about granting access are made by the Go release team at Google. If your request is declined, it is almost always because you haven't been active enough for them to get a clear enough signal about your work, understanding of project conventions, and so on. Don't lose heart: it can take time to reach that level of familiarity.
 
diff --git a/GithubAccess.md b/GithubAccess.md
index 6d6dd0c..b7a9a57 100644
--- a/GithubAccess.md
+++ b/GithubAccess.md
@@ -22,7 +22,7 @@
 
 ## Requesting Access
 
-To get request either of the access types above, file a bug (https://github.com/golang/go/issues/new?title=access:+&body=See+https://go.dev/wiki/GithubAccess) and list and state which access you want (its name and group URL).
+To request any of the access types above, file a new issue (https://go.dev/issue/new?title=access:+&body=See+https://go.dev/wiki/GithubAccess.) and state which access you want (its name and group URL).
 
 ## Once you have access
 
diff --git a/Gomote.md b/Gomote.md
index 33f70e6..29c6c82 100644
--- a/Gomote.md
+++ b/Gomote.md
@@ -234,7 +234,7 @@
 
 **On August 2022, a new infrastructure was deployed which required the removal of all gomote access from previously approved users. Please re-request access if you still require access.**
 
-To gain access to the gomote service, file an issue with `access: gomote` as the title and cc `@golang/release`. The issue should contain an email address to a google account. The provided account will only be used for authentication purposes.
+To request access to the gomote service, file a new issue (https://go.dev/issue/new?title=access:+&body=See+https://go.dev/wiki/Gomote%23access.) and state the Google account you use to log in to Gerrit. The provided account will only be used for authentication purposes.
 
 Authentication is triggered with the first invocation of a command: