Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Merged
merged 2 commits into from
Aug 14, 2024
Merged

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

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
878f630
typo: fix incorrect usage of it's
trent-s Aug 13, 2024
5f0ed0c
Merge branch 'Green-Software-Foundation:dev' into dev
trent-s Aug 13, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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!

Expand Down
4 changes: 2 additions & 2 deletions casdk-docs/docs/architecture/data-sources.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down Expand Up @@ -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.

Expand Down
Loading