chore: update documentation

Author: rubencarvalho

CONTRIBUTOR-DOCS/01_contributor-guides/06_releasing-swc.md

@@ -98,27 +98,48 @@ If not logged in, run `npm login` to sign in to your account.
 
 ## Releasing to NPM — the good stuff
 
-The publishing workflow is handled by a single unified script (`scripts/publish.js`) that publishes both 1st-gen and 2nd-gen packages. The script handles building, versioning, publishing, and git operations automatically.
-
-1. Run `git checkout main && git fetch && git pull && git clean -dfX` to ensure you are working with the latest code
-2. Run `yarn install && yarn build` to install all dependencies and build the pre-processed assets for publication.
-    1. Confirm no files were updated or modified
-3. Scan the version summary for any unexpected changes
-    1. In your IDE search `': major` , `': minor`, `': patch` , based on the results in the order of this search list, the highest level takes precedence
-        1. exclude files: `.changeset/README.md`
-4. Open your authenticator app to have it ready
-5. Run one of the following commands depending on the type of release:
-    - **Regular release:** `yarn publish` (creates git tags, publishes both 1st-gen and 2nd-gen)
-    - **Snapshot release:** `yarn publish:snapshot` (no git tags, uses `snapshot` npm tag)
-6. Enter the one-time password from your authenticator for NPM.
-    1. Wait for a fresh password; a stale timer might cause issues.
-7. After the SWC packages are released, the React Wrapper packages will be generated.
-    1. This multi-phase approach ensures that the wrapped packages share the same version as the standard packages.
-8. Enter a new one-time password from your authenticator for NPM.
-9. For regular releases, the `yarn publish` command will automatically commit the changes to main with a commit message of `chore: release new versions #publish`
-    1. The docs site will publish automatically if the `#publish` string is included in the commit message and the check suite runs successfully.
-    2. For snapshot/nightly releases, no git operations are performed.
-10. Confirm the build on `main` passes (regular releases only)
+The publishing workflow is handled by a single unified script (`scripts/publish.js`) that automates the entire process: cleaning, building, versioning, publishing, and git operations.
+
+1. **Prepare your workspace:**
+    - Run `git checkout main && git fetch && git pull` to ensure you have the latest code
+    - Confirm the working directory is clean with `git status`
+2. **Review changesets:**
+    - Scan the `.changeset` directory for pending changes
+    - In your IDE search `': major`, `': minor`, `': patch` to verify the release impact
+        - Exclude files: `.changeset/README.md`
+        - The highest level takes precedence (major > minor > patch)
+    - Confirm the changes match your expectations
+3. **Prepare for publishing:**
+    - Open your authenticator app to have it ready
+    - You'll need to enter a one-time password twice during the process:
+        1. Once for the main SWC packages
+        2. Once for the React wrapper packages
+4. **Run the publish command:**
+    - **Regular release:** `yarn publish`
+        - Creates git tags
+        - Publishes to npm with `latest` tag
+        - Commits changes to `main`
+    - **Snapshot release:** `yarn publish:snapshot`
+        - No git tags
+        - Publishes to npm with `snapshot` tag
+        - No git commits
+    - **Custom tag release:** `node ./scripts/publish.js --snapshot --tag beta`
+        - No git tags
+        - Publishes to npm with custom tag (e.g., `beta`, `alpha`, `rc`, `nightly`)
+        - No git commits
+5. **What happens during publishing:**
+    1. The script cleans all build artifacts and reinstalls dependencies
+    2. Builds all packages (1st-gen and 2nd-gen)
+    3. Generates custom elements manifests
+    4. Versions packages with changesets
+    5. Publishes to npm (you'll enter your first OTP here)
+    6. Builds React wrapper packages
+    7. Publishes React wrappers to npm (you'll enter your second OTP here)
+    8. For regular releases: commits changes and creates git tags
+6. **Verify the release:**
+    - For regular releases, confirm the build on `main` passes
+    - Check the [tags page](https://github.com/adobe/spectrum-web-components/tags) to verify new tags were created
+    - The docs site will publish automatically if the commit message includes `#publish` and checks pass
 
 ### Troubleshooting
 
@@ -127,9 +148,9 @@ If publishing fails with an error:
 - Check the [list of tags](https://github.com/adobe/spectrum-web-components/tags) to see if new tags have been released for your publishing attempt.
 - If they were, run `yarn publish` again (or the appropriate command for your release type).
 
-### Advanced: Custom npm tags
+### Custom npm tags
 
-For special releases like beta, alpha, or release candidates, you can use custom npm tags:
+For special releases like beta, alpha, nightly, or release candidates, you can use custom npm tags with the `--snapshot` and `--tag` flags:
 
 ```bash
 # Beta release
@@ -138,16 +159,20 @@ node ./scripts/publish.js --snapshot --tag beta
 # Alpha release
 node ./scripts/publish.js --snapshot --tag alpha
 
+# Nightly release
+node ./scripts/publish.js --snapshot --tag nightly
+
 # Release candidate
 node ./scripts/publish.js --snapshot --tag rc
 ```
 
 Users can then install these versions with:
 
 ```bash
-yarn install @spectrum-web-components/button@beta
-yarn install @spectrum-web-components/button@alpha
-yarn install @spectrum-web-components/button@rc
+yarn add @spectrum-web-components/button@beta
+yarn add @spectrum-web-components/button@alpha
+yarn add @spectrum-web-components/button@nightly
+yarn add @spectrum-web-components/button@rc
 ```
 
 ---