improve github token generation section (#1012)

I actually started to follow the wiks using the docs, and only then noticed there's this convenient direct link to creating a token

Author: vzaidman

docs/guide-release-testing.md

@@ -59,21 +59,21 @@ Followed by the options:
   -c, --ciToken                                                         [string]
 ```
 
-Using the `-c <your-token>` option is recommended, as the script will download the required artifacts from Github, instead of having to build from source reducing the testing time. It's suggested to store your [Github Personal Access Token (classic)](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#personal-access-tokens-classic) using:
-
-```bash
-export GITHUB_TOKEN=<token>
-```
+Using the `-c <your-token>` option is recommended, as the script will download the required artifacts from GitHub, instead of having to build from source reducing the testing time.
 
 > [!Warning]
 > If you are testing versions of React Native that are < 0.75, you need a CircleCI token rather than a GitHub Token.
 > Follow [these instruction](https://circleci.com/docs/managing-api-tokens/) to learn how to create one.
 
-Use [this link](https://github.com/settings/tokens/new?description=React%20Native%20Releases&scopes=repo) to generate a token with the Repo scope.
+Use [this link](https://github.com/settings/tokens/new?description=React%20Native%20Releases&scopes=repo) to generate a token with the Repo scope. Then you can store it using:
+
+```bash
+export GITHUB_TOKEN=<token>
+```
 
 There are a couple of extra requirements to make this flow work:
 
-1. the CI must have run at least once in the current branch. We need to download artifacts generated by Github, so we need to have at least one run of the CI.
+1. the CI must have run at least once in the current branch. We need to download artifacts generated by GitHub, so we need to have at least one run of the CI.
 2. The relevant jobs must have been finished. The required jobs depends on the task you are about to test:
    - if you are testing RNTester on iOS, it has to download Hermes for iOS. So the job that produces it must have finished successfully
    - if you are testing RNTester on Android, it has to download the right APK (JSC or Hermes). So the job that produces the APKs must have finished successfully.
@@ -84,7 +84,7 @@ If any of those prerequisites is not met, the script should output a proper erro
 > [!Warning]
 > CI artifacts are only taken from the _last_ commit. This means everytime you push to your release branch, you'll have to wait for the artifacts to build again. You cannot release test using artifacts from an "older" commit. Plan accordingly.
 
-If you need to build React Native from source, you can skip the `-c` parameter. By not passing the Github token, the script falls back to the previous flow, building everything locally.
+If you need to build React Native from source, you can skip the `-c` parameter. By not passing the GitHub token, the script falls back to the previous flow, building everything locally.
 
 ## Dimensions to test (RN >= 0.79)