Merge branch 'cguindon/master/github-update-access' into 'master'

Update Access to GitHub Repositories section

See merge request eclipse/dash/org.eclipse.dash.handbook!3

source/chapters/resources.adoc

@@ -183,7 +183,7 @@ To gain write access to a project's GitHub repositories a developer must:
 * Be <<elections-committer, elected>> as a project committer; and
 * Provide their GitHub Id in their <<contributing-account,Eclipse Foundation Account>>.
 
-Project leads are granted `admin` level access to their project's GitHub repositories.
+Project leads are granted `maintain` level access to their project's GitHub repositories. However, it's possible for them to request temporary access to the "admin" level by {helpdeskUrl}[creating an issue]. The issue must describe what will be done using this new level of access and how long it will be needed.
 
 [#resources-gerrit]
 === Gerrit Code Review
@@ -362,4 +362,4 @@ Yes.
 
 Can an {aForgeName} project accept anonymous code contributions? ::
 
-No. All contributions must be associated with their author using their legal name and a real email address. In pragmatic terms, the contributor must provide their legal name and email address in the Git commit's `Author` field; the contributor must also have electronically signed the ECA using those same credentials.
+No. All contributions must be associated with their author using their legal name and a real email address. In pragmatic terms, the contributor must provide their legal name and email address in the Git commit's `Author` field; the contributor must also have electronically signed the ECA using those same credentials.
\ No newline at end of file