patch(release_*.yaml): Fix comment in docs

.github/workflows/release_charm.md

@@ -28,7 +28,7 @@ jobs:
     secrets:
       charmhub-token: ${{ secrets.CHARMHUB_TOKEN }}
     permissions:
-      contents: write  # Needed to create GitHub release
+      contents: write  # Needed to create git tags
 ```
 
 ### metadata.yaml required
@@ -44,4 +44,4 @@ With "unified charmcraft.yaml syntax", charmcraft extracts the data back into ac
 Benefits of separate files:
 - no difference in files between source repository and *.charm artifact that would be confusing to developers
 - comments in YAML files retained
-- charmcraft just copies the files into the *.charm artifact, instead of using more complicated logic to extract that information (which would create more surface area for bugs)
+- charmcraft just copies the files into the *.charm artifact, instead of using more complicated logic to extract that information (which would create more surface area for bugs)

.github/workflows/release_rock.md

@@ -30,7 +30,7 @@ jobs:
       artifact-prefix: ${{ needs.build.outputs.artifact-prefix }}
     permissions:
       packages: write  # Needed to publish to GitHub Container Registry
-      contents: write  # Needed to create GitHub release
+      contents: write  # Needed to create git tags
 ```
 
 Grant package `Write` role to GitHub Actions for the source GitHub repository: https://docs.github.com/en/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package

.github/workflows/release_snap.md

@@ -32,7 +32,7 @@ jobs:
     secrets:
       snap-store-token: ${{ secrets.SNAP_STORE_TOKEN }}
     permissions:
-      contents: write  # Needed to create GitHub release
+      contents: write  # Needed to create git tags
 ```
 
 `SNAP_STORE_TOKEN` should be generated with `SNAPCRAFT_STORE_AUTH=candid` (e.g. `SNAPCRAFT_STORE_AUTH=candid snapcraft export-login`)