You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know this is a fairly minor issue, but there are three places in the documentation where "it's" is used incorrectly, and should be replaced with "its". (I only notice this because I often catch myself making the same mistake.)
I will submit a PR shortly to resolve this issue. The three proposed changes are as follows:
File: README.md
Original: The Carbon Aware SDK at it's core sits firmly in the Tooling pillar,
Proposed: The Carbon Aware SDK at its core sits firmly in the Tooling pillar,
File: casdk-docs/docs/architecture/data-sources.md
Original: within it's implementation.
Proposed: within its implementation.
File: casdk-docs/docs/architecture/data-sources.md
Original: under it's purview
Proposed: under its purview
Thank you for your ongoing efforts and consideration of this change.
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Contact Details
[email protected]
Overview of Change
I know this is a fairly minor issue, but there are three places in the documentation where "it's" is used incorrectly, and should be replaced with "its". (I only notice this because I often catch myself making the same mistake.)
I will submit a PR shortly to resolve this issue. The three proposed changes are as follows:
File: README.md
Original: The Carbon Aware SDK at it's core sits firmly in the Tooling pillar,
Proposed: The Carbon Aware SDK at its core sits firmly in the Tooling pillar,
File: casdk-docs/docs/architecture/data-sources.md
Original: within it's implementation.
Proposed: within its implementation.
File: casdk-docs/docs/architecture/data-sources.md
Original: under it's purview
Proposed: under its purview
Thank you for your ongoing efforts and consideration of this change.
Code of Conduct
The text was updated successfully, but these errors were encountered: