Merge pull request #62 from vipulnsward/typos

Fix some typos and github => GitHub

Author: Zachary Scott

README.md

@@ -27,7 +27,7 @@ recipes that have been requested or are in progress.
 
 ## Here's the run down
 
-To get started you should clone the repository from github:
+To get started you should clone the repository from GitHub:
 
 ```bash
 git clone git://github.com/sinatra/sinatra-recipes.git

app.rb

@@ -222,7 +222,7 @@ def get_activity_by_author
             p
               |Browse the <a href="/activity">latest activity</a>
             p
-              | These recipes are provided by the following outsanding members of the Sinatra 
+              | These recipes are provided by the following outstanding members of the Sinatra
               | community:
             dl id="contributors"
               - @contributors.each do |contributor|

deployment/dreamhost_via_passenger.md

@@ -65,7 +65,7 @@ The solution is to explicitly require the rack and sinatra gems in your
 config.ru. Add the following two lines to the start of your config.ru file:
 
 ```ruby
-require '/home/USERNAME/.gem/ruby/1.8/gems/rack-VERSION-OF-RACK-GEM-YOU-HAVE-INSTALLELD/lib/rack.rb'
-require '/home/USERNAME/.gem/ruby/1.8/gems/sinatra-VERSION-OF-SINATRA-GEM-YOU-HAVE-INSTALLELD/lib/sinatra.rb'
+require '/home/USERNAME/.gem/ruby/1.8/gems/rack-VERSION-OF-RACK-GEM-YOU-HAVE-INSTALLED/lib/rack.rb'
+require '/home/USERNAME/.gem/ruby/1.8/gems/sinatra-VERSION-OF-SINATRA-GEM-YOU-HAVE-INSTALLED/lib/sinatra.rb'
 ```
 

deployment/nginx_proxied_to_unicorn.md

@@ -267,7 +267,7 @@ information on stopping the server look into `man ps` and `man kill`.
 
 ### Resources
 
-*   [unicorn source on github](http://github.com/defunkt/unicorn)
+*   [unicorn source on GitHub](http://github.com/defunkt/unicorn)
 *   [original unicorn announcement](http://github.com/blog/517-unicorn)
 *   [official unicorn homepage](http://unicorn.bogomips.org/)
 *   [unicorn rdoc](http://rdoc.info/gems/unicorn/2.0.0/frames)

development/bundler.md

@@ -117,7 +117,7 @@ Requiring `bundler/setup` is the same as calling `Bundler.setup` yourself, and
 is the recommended method in the gembundler documentation.
 
 ```ruby
-# If you're using Ruby 1.9 you'll need to specifially load rubygems
+# If you're using Ruby 1.9 you'll need to specifically load rubygems
 require 'rubygems'
 
 # and now load bundler with your dependencies load paths

development/i18n.md

@@ -12,7 +12,7 @@ The following configuration is necessary on I18n so that:
 
   * it can fallback on other locales if the requested one is not
     available (ie: translation does not exist).
-  * all the transalations are read from YAML files located in the
+  * all the translations are read from YAML files located in the
     `locales` directory
 
 ```ruby
@@ -25,7 +25,7 @@ end
 
 Now we need to choose the locale that the user wants. There are several
 solutions (and some can even be mixed together): browser preference,
-spefic URL, dedicated subdomain, cookies/session management. 
+specific URL, dedicated subdomain, cookies/session management.
 Only the first three will be shown below:
 
 ### Browser preference (requires `rack-contrib`)

embed/event-machine.md

@@ -2,7 +2,7 @@
 
 EventMachine is a very useful tool and sometimes you need to add a web-interface
 on top of it. Yes, EM does support this out of the box, but it can be ugly and
-hard to work with. Why not use somethig that everyone already knows and loves
+hard to work with. Why not use something that everyone already knows and loves
 like Sinatra?
 
 Below is a (working) code-sample for running a simple HelloWorld Sinatra app
@@ -120,6 +120,6 @@ ab -c 10 -n 100 http://localhost:8181/delayed-hello
 If this finishes in "zero point something" seconds, then you have successfully
 setup Sinatra to run within EM and you are taking requests on the event-loop
 and deferring tasks to the background. If it takes any longer than that, then
-you are most likely taking requetss in the background which means when the EM
+you are most likely taking requests in the background which means when the EM
 queue fills up, you can't process your sinatra requests (not a good thing!).
 Make sure that you have threaded set to false and then try again.

helpers/partials_using_the_sinatra-partial_gem.md

@@ -44,4 +44,4 @@ end
 ### More information
 
 For more configuration options and usage,
-[view the sinatra-partial gem in github](https://github.com/yb66/Sinatra-Partial).
+[view the sinatra-partial gem on GitHub](https://github.com/yb66/Sinatra-Partial).

middleware/rack_parser.md

@@ -20,7 +20,7 @@ And your Message model would have an appropriate `#from_hash` method that
 grabs what it needs from the parsed message and throws it into a new instance.
 
 If your application has several different endpoints, all using the same 
-content-type, you could save some repitition by moving it to a helper:
+content-type, you could save some repetition by moving it to a helper:
 
 ```ruby
 helpers do
@@ -43,7 +43,7 @@ the parsing logic out of your application itself starts to become attractive.
 One option is to move it into a module that your app extends.
 
 But another option is to do the parsing in a middleware. That way, your app is
-not resposible for doing the basic parsing at all -- it's done and exposed to 
+not responsible for doing the basic parsing at all -- it's done and exposed to
 your app by the time the request arrives.
 
 The idea is *to mimic what Rack does to process form data*, which is to populate

testing/capybara_with_steak.md

@@ -39,7 +39,7 @@ end
 
 **Steak Resources**
 
-*   [Source on github](https://github.com/cavalle/steak)
+*   [Source on GitHub](https://github.com/cavalle/steak)
 *   [Documentation](http://rdoc.info/gems/steak/1.0.1/frames/)
 *   [Timeless: BDD with RSpec and Steak](http://timeless.judofyr.net/bdd-with-rspec-and-steak)
 *   [More Steak Resources](https://github.com/cavalle/steak/wiki/Resources)