diff --git a/page/code-organization/feature-browser-detection.md b/page/code-organization/feature-browser-detection.md
index 67d7040d..5b29f511 100644
--- a/page/code-organization/feature-browser-detection.md
+++ b/page/code-organization/feature-browser-detection.md
@@ -104,7 +104,7 @@ That's it. Easy.
 
 So, while the Modernizr syntax is great, it can end up being quite cumbersome to have several conditionals. Secondly, we're sending the code for both conditions to every browser, regardless if we'll need it or not.
 
-The `Modernizr` object exposes a `load()` method that many prefer over the syntax mentioned previously. This is due to the another library that Modernizr now uses internally: [yepnope](http://yepnopejs.com/). Testing for canvas can now become something like this:
+The `Modernizr` object exposes a `load()` method that many prefer over the syntax mentioned previously. This is due to another library that Modernizr now uses internally: [yepnope](http://yepnopejs.com/). Testing for canvas can now become something like this:
 
 ```
 Modernizr.load({
diff --git a/page/events/triggering-event-handlers.md b/page/events/triggering-event-handlers.md
index b4a55a0b..648eec89 100644
--- a/page/events/triggering-event-handlers.md
+++ b/page/events/triggering-event-handlers.md
@@ -75,5 +75,5 @@ $( "p" ).on( "click", foo );
 foo(); // instead of $( "p" ).trigger( "click" )
 ```
 
-A more complex architecture can built on top of trigger using the [publish-subscribe pattern](http://en.wikipedia.org/wiki/Publish%E2%80%93subscribe_pattern) using [jQuery plugins](https://gist.github.com/661855).
+A more complex architecture can be built on top of trigger using the [publish-subscribe pattern](http://en.wikipedia.org/wiki/Publish%E2%80%93subscribe_pattern) using [jQuery plugins](https://gist.github.com/661855).
 With this technique, `.trigger()` can be used to notify other sections of code that an application specific event has happened.