Fix typos and improve grammar on some getting started guides

Author: carlosantoniodasilva

getting-started/try-catch-and-rescue.markdown

@@ -95,7 +95,7 @@ In Elixir, we avoid using `try/rescue` because **we don't use errors for control
 
 In Elixir, a value can be thrown and later be caught. `throw` and `catch` are reserved for situations where it is not possible to retrieve a value unless by using `throw` and `catch`.
 
-Those situations are quite uncommon in practice except when interfacing with libraries that does not provide a proper API. For example, let's imagine the `Enum` module did not provide any API for finding a value and that we needed to find the first multiple of 13 in a list of numbers:
+Those situations are quite uncommon in practice except when interfacing with libraries that do not provide a proper API. For example, let's imagine the `Enum` module did not provide any API for finding a value and that we needed to find the first multiple of 13 in a list of numbers:
 
 ```iex
 iex> try do

getting-started/typespecs-and-behaviours.markdown

@@ -90,9 +90,9 @@ Typespecs are not only useful to developers and as additional documentation. The
 
 ## Behaviours
 
-Many modules share the same public API. Take a look at [Plug](https://github.com/elixir-lang/plug), which, as it description states, is a **specification** for composable modules in web applications. Each *plug* is a module which **has to** implement at least two public functions: `init/1` and `call/2`.
+Many modules share the same public API. Take a look at [Plug](https://github.com/elixir-lang/plug), which, as its description states, is a **specification** for composable modules in web applications. Each *plug* is a module which **has to** implement at least two public functions: `init/1` and `call/2`.
 
-Behaviors provide a way to:
+Behaviours provide a way to:
 
 * define a set of functions that have to be implemented by a module;
 * ensure that a module implements all the functions in that set.
@@ -101,7 +101,7 @@ If you have to, you can think of behaviours like interfaces in object oriented l
 
 ### Defining behaviours
 
-Say we want to implement a bunch of parsers, each parsing structured data: for example, a JSON parser and a YAML parser. Each of these two parsers will *behave* the same way: both will provide a `parse/1` function and a `extensions/0` function. The `parse/1` function will return an Elixir representation of the structured data, while the `extensions/0` function will return a list of file extensions that can be used for each type of data (e.g., `.json` for JSON files).
+Say we want to implement a bunch of parsers, each parsing structured data: for example, a JSON parser and a YAML parser. Each of these two parsers will *behave* the same way: both will provide a `parse/1` function and an `extensions/0` function. The `parse/1` function will return an Elixir representation of the structured data, while the `extensions/0` function will return a list of file extensions that can be used for each type of data (e.g., `.json` for JSON files).
 
 We can create a `Parser` behaviour:
 

getting-started/where-to-go-next.markdown

@@ -28,7 +28,7 @@ Elixir is an extensible and very customizable programming language thanks to its
 
 ## Community and other resources
 
-We have a [Learning](/learning.html) section that explores books, screencasts and other resources for learning Elixir and explore the ecossystem. There are also plenty of Elixir resources out there, like conference talks, open source projects, and other learning material produced by the community.
+We have a [Learning](/learning.html) section that explores books, screencasts and other resources for learning Elixir and explore the ecosystem. There are also plenty of Elixir resources out there, like conference talks, open source projects, and other learning material produced by the community.
 
 Remember that in case of any difficulties, you can always visit the **#elixir-lang** channel on **irc.freenode.net** or send a message to the [mailing list](http://groups.google.com/group/elixir-lang-talk). You can be sure that there will be someone willing to help. To keep posted on the latest news and announcements, follow the [blog](/blog/) and follow the language development on the [elixir-core mailing list](http://groups.google.com/group/elixir-lang-core).