Merge pull request #553 from trent-s/dev

Documentation: "it's" is used incorrectly several times

README.md

@@ -18,7 +18,7 @@ By knowing the carbon emissions of the energy that powers your applications, you
 * Using data to run hypothetical models to understand how you could start driving impact and reduce emissions, drive business cases for change, and create a greener future. 
 
 
-Within the [Green Software Foundations Theory of Change](https://greensoftware.foundation/articles/theory-of-change), we look at 3 pillars, that being **Knowledge**, **Tech Culture**, and **Tooling** as focus areas to drive this change.  The Carbon Aware SDK at it's core sits firmly in the **Tooling** pillar, and also supports the other pillars, providing **Knowledge** through emissions data to inform change, and being core enabler for the **Tech Culture** for building carbon aware software.
+Within the [Green Software Foundations Theory of Change](https://greensoftware.foundation/articles/theory-of-change), we look at 3 pillars, that being **Knowledge**, **Tech Culture**, and **Tooling** as focus areas to drive this change.  The Carbon Aware SDK at its core sits firmly in the **Tooling** pillar, and also supports the other pillars, providing **Knowledge** through emissions data to inform change, and being core enabler for the **Tech Culture** for building carbon aware software.
 
 Companies including UBS and Vestas have already deployed the Carbon Aware SDK to build greener software, and you can too!
 

casdk-docs/docs/architecture/data-sources.md

@@ -23,7 +23,7 @@ handle these calls, only the data source should have access to, and knowledge
 of, that client.
 
 - For example, the WattTimeDataSource has a reference to a private
-  WattTimeClient within it's implementation. The WattTimeClient handles the HTTP
+  WattTimeClient within its implementation. The WattTimeClient handles the HTTP
   GET/POST calls to WattTime and the data source invokes the client once it has
   processed the request, and then processes the response before returning a
   final result.
@@ -82,7 +82,7 @@ dotnet add package Microsoft.Extensions.DependencyInjection
 
 Each new data source should extend from a generic data source interface. A data
 source interface defines all the parameters and functions that any data source
-that falls under it's purview must define/implement. By defining the interface,
+that falls under its purview must define/implement. By defining the interface,
 it allows the SDK to switch between the set of data sources seamlessly because
 they all share the same input functions and output types.