From 70d36d938c891ad5e4c7ea149e10b12c9b083c4a Mon Sep 17 00:00:00 2001
From: Tyler Yahn <MrAlias@users.noreply.github.com>
Date: Fri, 10 Jul 2020 11:30:39 -0700
Subject: [PATCH] Update RELEASING.md with correct tag.sh cmd (#130)

---
 RELEASING.md | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/RELEASING.md b/RELEASING.md
index a6a55903b9b..54f633567b5 100644
--- a/RELEASING.md
+++ b/RELEASING.md
@@ -69,17 +69,22 @@ In nearly all cases, `<new_contrib_tag>` should be the same as
 Now create a `<new_contrib_tag>` on the commit hash of the changes made in pre-release step,
 
 1. Run the tag.sh script.
+
+    ```
+    ./tag.sh <new_contrib_tag> <commit-hash>
+    ```
 2. Push tags upstream. Make sure you push upstream for all the sub-module tags as well.
 
     ```
-    ./tag.sh -t <new_contrib_tag> -c <commit-hash>
     git push upstream <new_contrib_tag>
     git push upstream <submodules-path/new_contrib_tag>
+    ...
     ```
 
 ## Release
-Now create a release for the new `<new_contrib_tag>` on github. tag.sh script generates commit logs since
-last release. Use that to draft the new release.
+Now create a release for the new `<new_contrib_tag>` on github.
+The release body should include all the release notes in the Changelog for this release.
+Additionally, the `tag.sh` script generates commit logs since last release which can be used to suppliment the release notes.
 
 <!-- ## Verify Examples -->
 <!-- After releasing run following script to verify that examples build outside of the otel repo. -->