Typo fixes in markdown and javadoc as suggested by intellij typo inspection.

--
MOS_MIGRATED_REVID=128476121

2 files changed, 2 insertions, 2 deletions

diff --git a/site/blog/_posts/2016-06-10-0.3.0-release.md b/site/blog/_posts/2016-06-10-0.3.0-release.md
index 2038c98ac4..bbec6264bf 100644
--- a/site/blog/_posts/2016-06-10-0.3.0-release.md
+++ b/site/blog/_posts/2016-06-10-0.3.0-release.md
@@ -78,7 +78,7 @@ Looking ahead to 0.4.0:
 A big thank you to our community for your continued support. Particular
 shout-outs to the following contributors:
 
-* [Justine Tunney](https://github.com/jart) - for developping and maintaining
+* [Justine Tunney](https://github.com/jart) - for developing and maintaining
   the [Closure JS rules](https://github.com/bazelbuild/rules_closure) of Bazel.
 * [Alpha Lam](https://github.com/hhclam) - for implementing remote
   caching/execution and following up on these features.
diff --git a/site/blog/_posts/2016-06-10-ide-support.md b/site/blog/_posts/2016-06-10-ide-support.md
index 11dadc27d2..6d0f7cc881 100644
--- a/site/blog/_posts/2016-06-10-ide-support.md
+++ b/site/blog/_posts/2016-06-10-ide-support.md
@@ -35,7 +35,7 @@ In the 0.3.0 Bazel release, we are adding a new concept to Bazel -
 [_aspects_](/docs/skylark/aspects.html).
 Aspects allow augmenting build dependency graphs with additional information
 and actions. Applying an aspect to a build target creates a "shadow
-dependency graph" reflecting all transitive depenedencies of that target,
+dependency graph" reflecting all transitive dependencies of that target,
 and the aspect's implementation determines the actions that Bazel executes
 while traversing that graph.
 The [documentation on aspects](/docs/skylark/aspects.html) explains this in more