use github.token instead of secrets.GITHUB_TOKEN in examples

Author: zefir-git

README.md

@@ -12,7 +12,7 @@ steps:
     uses: cloudnode-pro/[email protected]
     with:
       # See the ‘Inputs’ section below for details.
-      gh-token: ${{ secrets.GITHUB_TOKEN }}
+      gh-token: ${{ github.token }}
       release-id: 123456 # Optional for `release` events.
       files: |
         path/to/file.txt; type=text/plain; name=File1.txt
@@ -25,7 +25,7 @@ steps:
 
 The GitHub token to use for authentication.
 
-If you are uploading to a release in the same repository, you can use `${{secrets.GITHUB_TOKEN}}`, which is a secret
+If you are uploading to a release in the same repository, you can use `${{github.token}}`, which is a secret
 generated by the workflow. Otherwise, you need to manually create a token, save it as a repository secret, and pass it
 using `${{secrets.NAME_OF_SECRET}}`.