Update release docs (#934)

Signed-off-by: Ricky Saechao <[email protected]>

Author: RickyLB

RELEASE.md

@@ -5,8 +5,11 @@
 >- Prior authorization must be given by a maintainer of the crate
 
 ## Release
+
+In the main directory, use the the following steps to publish to [hedera](https://crates.io/crates/hedera): 
+
 1. Create a new git branch: `release/vX.Y.Z`.
-2. Run all tests against [hedera-local-node](https://github.com/hashgraph/hedera-local-node). Stop local-node once the tests are completed.
+2. Run all tests against [hiero-local-node](https://github.com/hiero-ledger/hiero-local-node). Stop local-node once the tests are completed.
 >- `cargo test`
 3. Change the version number in *Cargo.toml*.
 >- `version = major.minor.patch`
@@ -15,7 +18,10 @@
 >- `cargo publish --dry-run`
 5. If all warnings and error are resolved, publish the newest version to *crates.io*.
 >- `cargo publish`
-6. Create a new tag.
->- `git push -a <version> -m <version>`
-7. Once branch has been approved and merged to main, document added features pertaining to the newest release.
->- [Tags and Releases for Rust SDK](https://github.com/hashgraph/hedera-sdk-rust/releases)
+6. Once branch has been approved and merged to main, document added features pertaining to the newest release.
+7. Create the new tag in Github `vX.Y.Z`
+>- [Tags and Releases for Rust SDK](https://github.com/hiero-ledger/hiero-sdk-rust/releases)
+
+**Note** 
+- If there are new local changes to [`hedera-proto`](https://crates.io/crates/hedera-proto) crate, this must be published before `hedera` crate is published for each release. 
+Cargo will prevent publishing if this is the case.