docs: revise wording

Signed-off-by: Shiwei Zhang <[email protected]>

RELEASE_CHECKLIST.md

@@ -14,15 +14,15 @@ This document describes the checklist to publish a release through the [GitHub r
 4. Compose and revise the release note and optionally select `Set as a pre-release` depending on the version.
 5. Publish the release on GitHub.
 6. [A workflow](https://github.com/oras-project/oras-dotnet/actions/workflows/release-nuget.yml) will be triggered automatically after releasing (i.e. a new tag is create) for publishing the release to NuGet.
-7. Wait for NuGet validating the newly release package.
-8. Announce the release to the community.
+7. Wait for NuGet to validate the newly release package.
+8. Announce the release in the community.
 
 ## Retract Process
 
 Due to many reasons (e.g. publish accidentally, security vulnerability discovered), a version can be retracted by the following steps:
 
 1. Determine the version to be retracted.
-2. Create an issue to vote for retraction as well as items to be retracted.
+2. Create an issue to vote for retraction as well as detailed items to be retracted.
 3. After the vote passes, delete or modify the release as well as the corresponding tag depending on the voted items.
 4. On `nuget.org`, [unlist](https://learn.microsoft.com/nuget/nuget-org/policies/deleting-packages) and / or [deprecate](https://learn.microsoft.com/nuget/nuget-org/deprecate-packages) the corresponding NuGet package.
-5. Announce the retraction to the community.
+5. Announce the retraction in the community.