[beam-site] 03/04: Addressed Ahmet's comments

[me...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

mergebot-role pushed a commit to branch mergebot
in repository https://gitbox.apache.org/repos/asf/beam-site.git

commit 77d3348f2d3cd6e332adae21dd1437328e7dd911
Author: Boyuan Zhang <bo...@google.com>
AuthorDate: Tue Aug 14 11:26:02 2018 -0700

    Addressed Ahmet's comments
---
 src/contribute/release-guide.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/src/contribute/release-guide.md b/src/contribute/release-guide.md
index 61e5502..aaffb28 100644
--- a/src/contribute/release-guide.md
+++ b/src/contribute/release-guide.md
@@ -304,7 +304,7 @@ There are 2 ways to trigger a nightly build, either using automation script(reco
       ./beam/release/src/main/scripts/start_snapshot_build.sh
 
 * Tasks included
-  1. Install [hub](https://github.com/github/hub) within your agreement.
+  1. Install [hub](https://github.com/github/hub) with your agreement.
   1. Touch an empty txt file and commit changes into ```${your remote beam repo}/snapshot_build```
   1. Use hub to create a PR against apache:master, which triggers a Jenkins job to build snapshot.
   
@@ -331,7 +331,7 @@ There are 2 ways to perform this verification, either running automation script(
       ./beam/release/src/main/scripts/verify_release_build.sh
 
 * Tasks included
-  1. Install ```pip```, ```virtualenv```, ```cython``` and ```/usr/bin/time``` within your agreements.
+  1. Install ```pip```, ```virtualenv```, ```cython``` and ```/usr/bin/time``` with your agreements.
   1. Run ```gradle release build``` against release branch.
   
 * Tasks you need to do manually
@@ -646,7 +646,7 @@ If there are no issues, reply on the vote thread to close the voting. Then, tall
 ### Run validation tests
 All tests listed in this [spreadsheet](https://s.apache.org/beam-release-validation)
 
-Since there are a bunch of tests, we recommend you running validatoins using automation script. In case of script failure, you can still run all of them manually.
+Since there are a bunch of tests, we recommend you running validations using automation script. In case of script failure, you can still run all of them manually.
 
 #### Run validations using run_rc_validation.sh
 * Script: [run_rc_validation.sh](https://github.com/apache/beam/blob/master/release/src/main/scripts/run_rc_validation.sh)