Merge branch 'dev' of https://github.com/change-code-io/docs into dev

Author: c-georgen

change-credits/cc-minting.md

@@ -3,7 +3,7 @@ label: Minting Change Credits
 order: -2
 ---
 
-Because Change Credits are only minted following confirmation of realized, tangible, and verifiable impact, there the process by which these assets are created follows a number of steps and involves multiple types of actors.
+Because Change Credits are only minted following confirmation of realized, tangible, and verifiable impact, the process by which these assets are created follows a number of steps and involves multiple types of actors.
 
 ### Participants
 
@@ -52,7 +52,7 @@ sequenceDiagram
 
 The above sequence diagram overviews how Change Credits are created. While the system supports alternative flows to facilitate various forms of financing, we can consider this base form to have x steps.
 
-1. The Good Generator submits an impact goal and plan for review by Change Code, as part of their onboarding process. Once approved to mint via the Changescape, the Good Generator mints their hypercert, signalling the beginning for their project.
+1. The Good Generator submits an impact goal and plan for review by Change Code, as part of their onboarding process. Once approved to mint via the Changescape, the Good Generator mints their hypercert, signaling the beginning for their project.
 2. After the projects' hypercert has been deployed, Change Code deploys an associated Token Bound Account (TBA) to act as a treasury for the project to receive funds into and mint tokens from.
 3. Partners begin contributing funds into the project's TBA in exchange for IOUs redeemable for Change Credits once the latter begin to be minted. These funds are then remitted to an account from which the Good Generator can spend to cover the costs of their work. This process can be done in an open-ended asynchronous manner, with funds being contributed to the project through the project's lifespan.
 4. As the Good Generator carries out their work to produce impact, they periodically submit evidence for review. This evidence is stored as records tied to their original hypercert and can be accessed by specified Verifiers.

change-credits/foundations.md

@@ -13,9 +13,13 @@ Before expanding on the architecture and processes involved in Change Credits di
 
 ### Hypercerts
 
-Hypercerts are on-chain, tokenized claims of positive impact. To be more precise, hypercerts represent *claims* of *work* done toward some beneficial outcome, be that work toward social or environmental impact or the building of a public good.
+Hypercerts are on-chain, tokenized claims of positive impact. To be more precise, hypercerts represent *claims* of *work* to be done toward some beneficial outcome, be that work toward social or environmental impact or the building of a public good.
 
-A complete list of the on-chain token data and off-chain metadata included in a hypercert can be found in the [documentation](https://hypercerts.org/docs/implementation/metadata). Importantly for our purposes and designs, there is no included support for verification that the work was completed or efficacious. This will therefore be addressed using another foundation public good, the Ethereum Attestation Service (EAS). However, the hypercerts specification does include a field for a list of contributors. Change Credits takes advantage of this encoding to record contributions of the actual work being done, while tracking *financial partners* through ownership of Change Credits themselves.
+!!!
+It is worth noting that the relationship between Hypercerts and the status of positive impact is not currently settled. Some usages lean toward only representing work already done while other implementations represent plans for future work as Hypercerts instead. Inside the Change Code implementation, we will default to the latter interpretation, with Hypercerts issued as a way to commit to future work.
+!!!
+
+A complete list of the on-chain token data and off-chain metadata included in a hypercert can be found in the [documentation](https://hypercerts.org/docs/implementation/metadata). Importantly, for our purposes and designs, there is no included support for verification that the work was completed or efficacious. This will therefore be addressed using another foundation public good, the Ethereum Attestation Service (EAS). However, the hypercerts specification does include a field for a list of contributors. Change Credits takes advantage of this encoding to record contributions of the actual work done, while tracking *financial partners* through ownership of Change Credits themselves.
 
 ### Ethereum Attestation Service (EAS)
 
@@ -28,7 +32,7 @@ While not tokens themselves (more on that [here](https://docs.attest.org/docs/co
 To maintain maximum compatibility across existing wallets and infrastructure, the Change Credits architecture leverages only broadly accepted ERC token standards. Change Credits themselves are minted as NFTs (non-fungible tokens) through the ERC721 standard.
 
 +++ ERC721
-ERC721 is the most widely adopted token standard for NFTs. The standard is well tested, and enjoys near universal support across wallet implementations.
+ERC721 is the most widely adopted token standard for NFTs. The standard is well-tested, and enjoys near-universal support across wallet implementations.
 +++ ERC1155
 Hypercerts adhere to the ERC1155 standard for semi-fungible tokens. This mixed standard, existing in the divide between fungible and non-fungible tokens, offers ideal flexibility for the unique requirements of the hypercerts standard.
 +++ ERC20

contributing/community-conduct.md

@@ -17,11 +17,11 @@ Examples of behavior that contributes to a positive environment for our communit
 * Being respectful of differing opinions, viewpoints, and experiences;
 * Giving and gracefully accepting constructive feedback;
 * Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience;
-* Focusing on what is best not just for us as individuals, but for the overall community;
+* Focusing on what is best not just for us as individuals but for the overall community;
 
 Examples of unacceptable behavior include:
 
-* The use of sexualized language or imagery, and sexual attention or advances of any kind;
+* The use of sexualized language or imagery and sexual attention or advances of any kind;
 * Trolling, insulting or derogatory comments, and personal or political attacks;
 * Public or private harassment;
 * Publishing others' private information, such as a physical or email address, or revealing any pseudonymous identity without their explicit permission;
@@ -33,7 +33,7 @@ Change Code's leadership is responsible for clarifying and enforcing our standar
 
 Change Code has the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
 
-Enforcement of this code will sometimes be a challenging exercise in judgement and conflicting values. We recognize that members may not always agree with a given course of action or remedy, but Change Code commits to always being transparent in how decisions have been made.
+Enforcement of this code will sometimes be a challenging exercise in judgment and conflicting values. We recognize that members may not always agree with a given course of action or remedy, but Change Code commits to always being transparent in how decisions have been made.
 
 ## Scope
 

contributing/contribution-guide.md

@@ -9,7 +9,7 @@ We are all people, all community members first, and developers second. All devel
 
 ## Contributing
 
-Change Code strives to work in public and release code as open source whenever possible. If you would like to contribute to any of our repositories just follow the steps below.
+Change Code strives to work in public and release code as open source whenever possible. If you would like to contribute to any of our repositories, just follow the steps below.
 
 1. Fork the repository.
 2. Create a new branch (`git checkout -b feature-branch-name`).
@@ -18,13 +18,13 @@ Change Code strives to work in public and release code as open source whenever p
 5. Push the code to your forked origin (`git push origin feature-branch-name`)
 6. Navigate back to the Change Code repository you forked from and create a new pull request.
 
-When making a pull request, do your best to describe the changes made and your motivations for doing so. While we're excited for your to participate alongside us, please understand that certain changes may not align with the our current roadmap or requirements. If we're unable to incorporate your work, we'll always do our best to explain why.
+When making a pull request, do your best to describe the changes made and your motivations for doing so. While we're excited for you to participate alongside us, please understand that certain changes may not align with the current roadmap or requirements. If we're unable to incorporate your work, we'll always do our best to explain why.
 
 To join our discussions, you can find us over on [Console](https://app.console.xyz/c/changecode). We always welcome new voices!
 
 ## Issue Reporting
 
-If you have a feature request or encounter a bug in any of our work, we invite you to report it with a Github issue in the relevant repository. We've provided pre-templates to help improve reporting.
+If you have a feature request or encounter a bug in any of our work, we invite you to report it with a GitHub issue in the relevant repository. We've provided pre-templates to help improve reporting.
 
 ## Commitment to Open Source Code
 

data-schemas/hypercerts.md

@@ -3,7 +3,7 @@ label: Hypercerts
 order: -1
 ---
 
-Change Code leverages the Hypercerts protocol, in turn developed from the ERC1155 token standard for semi-fungible tokens. While adhering to the requirements of the standard, Change Code modifies *how* some of the schema fields are used, adapting them to our theory of change and implementation needs.
+Change Code leverages the Hypercerts protocol, itself developed from the ERC1155 token standard for semi-fungible tokens. While adhering to the requirements of the standard, Change Code modifies *how* some of the schema fields are used, adapting them to our theory of change and implementation needs.
 
 ## ERC1155 Fields
 
@@ -22,7 +22,7 @@ work_scope
 :   A list of tasks to be done by the project. In development parlance this is a list of *outputs*--e.g. # of solar panels installed, kilos of supplies, $ of direct aid, # of vaccines.
 
 work_timeframe
-:   The time period during which the work for the project is to be carried out. In line with the Hypercerts standard, this is represented as an ordered pair of UTC timestamps.
+:   The time period during which the project work is to be carried out. In line with the Hypercerts standard, this is represented as an ordered pair of UTC timestamps.
 
 impact_scope
 :   Inside the Changescape `impact scope` is used to refer thematically to projects by category. For example, the [UN Sustainable Development Goals (SDGs)](https://sdgs.un.org/goals) or the [Ecological Benefits Framework (EBF)](https://ebfcommons.org/lex-icons/). Because the Hypercerts data is only aspirational, it would be premature to immutably publish indicators, which are instead reserved to be published only once verified inside Change Credits.

data-schemas/ious.md

@@ -5,10 +5,10 @@ order: -2
 
 IOUs are implemented as ERC20 (fungible) tokens, to maximize both compatibility with existing tools and to streamline the transferability of IOUs before they are redeemed for Change Credits.
 
-To define a batch of IOUs inside the Changescape the following specifications are made:
+To define a batch of IOUs inside the Changescape, the following specifications are made:
 
 Name | `CC IOU | {Good Generator} {Index}`
-:   The token name assigned to each batch of IOUs always begins with "CC IOU", this is then followed by the name of the Good Generator and an index. The purpose of the index is to differentiate between different projects from one Good Generator.
+:   The token name assigned to each batch of IOUs always begins with "CC IOU". This is then followed by the name of the Good Generator and an index. The purpose of the index is to differentiate between different projects from one Good Generator.
 
 Symbol | `CC-IOU-{ProjectID}`
 :   The abbreviated token symbol begins "CC-IOU" and is followed by a project ID, where the project ID is composed of the unique ID assigned to the project's Good Generator followed by the project's index value.

welcome.md

@@ -3,10 +3,10 @@ icon: rocket
 order: -1
 label: Welcome
 ---
-Welcome to the Change Code Knowledgebase. At Change Code we're building the tools for individuals and organizations to attest to and verify their impact and package that data into a meaningfully representative impact asset. Ultimately, the goal of these assets is to provide an unrestricted, but still accountable revenue stream, reducing the cost of social enterprise and eventually removing the need for continuous and unpredictable outside funding. Change Code is creating financial and data primitives that reliably and scalably represent impact outputs and just as important, longer-term impact outcomes—pioneering token-based representations of consumable and capital impact assets.
+Welcome to the Change Code Knowledgebase. At Change Code we're building the tools for individuals and organizations to attest to and verify their impact and package that data into a meaningfully representative impact asset. Ultimately, the goal of these assets is to provide an unrestricted but still accountable revenue stream, reducing the cost of social enterprise and eventually removing the need for continuous and unpredictable outside funding. Change Code is creating financial and data primitives that reliably and scalably represent impact outputs, and just as importantly, longer-term impact outcomes—pioneering token-based representations of consumable and capital impact assets.
 
-At the core of Change Code's work is our belief that in order to actualy achieve the world's sustainability and other impact goals, we must find a way to *make purpose profitable*. We are working to pioneer new financial primitives and tokenomics that will see impact itself emerge as the next asset class to be powered by web3.
+At the core of Change Code's work is our belief that in order to actually achieve the world's sustainability and other impact goals, we must find a way to *make purpose profitable*. We are working to pioneer new financial primitives and tokenomics that will see impact itself emerge as the next asset class to be powered by web3.
 
-The *Changescape* is a multi-chain and multi-token dApp (decentralized application) engineered to support the tokenization, verification, and ultimate monetization of a new asset category, postive impact.
+The *Changescape* is a multi-chain and multi-token dApp (decentralized application) engineered to support the tokenization, verification, and ultimate monetization of a new asset category, positive impact.
 
 If you're interested in contributing to our work, navigate over to the [Contributor Guide](./contributing/contribution-guide/).