Apply suggestions from code review

Therecanbeonlyone1969 · chaals · web-flow · commit a7d2a513ab12 · 2025-02-14T11:17:13.000-08:00
Co-authored-by: chaals &lt;chaals@users.noreply.github.com&gt;
diff --git a/community/contributors.md b/community/contributors.md
@@ -23,7 +23,7 @@ There is one other way to contribute, and it's the most important: **use the wor
 
 Here is the link to the Baseline Protocol code of conduct:
 
-{% embed url="https://github.com/ethereum-oasis-op/baseline/blob/master/CODE_OF_CONDUCT.md" %}
+{% embed url="https://github.com/ethereum-oasis-op/baseline/blob/main/CODE_OF_CONDUCT.md" %}
 
 ## Technical Contributors <a href="#technical-contributors" id="technical-contributors"></a>
 
diff --git a/docs/community/community-leaders/maintainers.md b/docs/community/community-leaders/maintainers.md
@@ -36,7 +36,7 @@ A Baseline Maintainer can become a Baseline Maintainer by doing the following,
 
 * Being an active Baseline Maintainer by actively attending the bi-weekly meetings
 * Making a contribution to the Baseline Protocol through [**BLIP work**](https://github.com/ethereum-oasis-op/baseline-blips), [**progressing the roadmap**](https://github.com/ethereum-oasis-op/baseline/blob/main/Baseline%20Protocol%20-%202022%20Roadmap.pdf), or other efforts
-* Then completing the [**Pull\_Request\_Template** ](https://github.com/ethereum-oasis-op/baseline/blob/main/.github/PULL\_REQUEST\_TEMPLATE.md)in its entirety to add users Github ID to the [**Code Owners file**](https://github.com/ethereum-oasis-op/baseline/blob/main/.github/CODEOWNERS)&#x20;
+* Then completing the [**Pull\_Request\_Template** ](https://github.com/ethereum-oasis-op/baseline/blob/main/.github/PULL\_REQUEST\_TEMPLATE.md)in its entirety to add users Github ID to the [**Code Owners file**](https://github.com/ethereum-oasis-op/baseline/blob/main/.github/CODEOWNERS)
 * The current Maintainers (listed Code Owners) will be assigned to review the Pull Request, and the PR will be merged once **two** Maintainers approve the request
 * If the Baseline Maintainer request is denied or poses concerns, the proposer or other Baseline Core Devs can escalate to the TSC
 
diff --git a/docs/community/governance.md b/docs/community/governance.md
@@ -4,13 +4,13 @@
 
 OASIS Open is a non-profit, vendor-neutral standards developing organization. It provides rules and guidelines to ensure equitable and transparent oversight of technical collaborations in open source and open standards. Additionally, it provides services such as technical program support, legal, marketing, and events management.
 
-The Baseline Protocol is governed by the [EEA Community Projects Project Governing Board (PGB)](https://github.com/ethereum-oasis-op/managed-open-project/blob/main/PROJECT-GOVERNING-BOARD.md) under the [OASIS Open Projects Program](http://oasis-open-projects.org/). EEA Community Projects exists to provide a neutral forum for companies and community representatives to create high-quality specifications that facilitate Ethereum’s longevity, interoperability, and ease of integration. One does not have to "join" the group formally or financially in order to make a contribution to Baseline or other Ethereum OASIS projects.
+The Baseline Protocol is governed by the [Ethereum OASIS Projects Project Governing Board (PGB)](https://github.com/ethereum-oasis-op/managed-open-project/blob/main/PROJECT-GOVERNING-BOARD.md) under the [OASIS Open Projects Program](http://oasis-open-projects.org/). EEA Community Projects exists to provide a neutral forum for companies and community representatives to create high-quality specifications that facilitate Ethereum’s longevity, interoperability, and ease of integration. One does not have to "join" the group formally or financially in order to make a contribution to Baseline or other Ethereum OASIS projects.
 
 Additional documentation about the OASIS Open Projects program can be found [here](https://github.com/oasis-open-projects/documentation).
 
 ## License and Patent Policies <a id="license-and-patent-policies"></a>
 
-All repos in the EEA Community Projects organization, including Baseline Protocol repositories, adhere to OASIS Open Projects [license](https://github.com/oasis-open-projects/documentation/blob/master/policy/licenses.md) and [patent polices](https://github.com/oasis-open-projects/documentation/blob/master/policy/call-for-patent-disclosure.md).
+All repos in the Ethereum OASIS Projects organization, including Baseline Protocol repositories, adhere to OASIS Open Projects [license](https://github.com/oasis-open-projects/documentation/blob/master/policy/licenses.md) and [patent polices](https://github.com/oasis-open-projects/documentation/blob/master/policy/call-for-patent-disclosure.md).
 
 In order to ensure clean IPR that allows Baseline to remain an open technology, OASIS rules require an [Entity CLA](https://www.oasis-open.org/open-projects/cla/entity-cla-20210630/) for persons or organizations contributing on behalf of a legal entity, and an [Individual CLA](https://cla-assistant.io/ethereum-oasis-op/managed-open-project) for community contributions. You must [sign the ICLA](https://cla-assistant.io/ethereum-oasis-op/managed-open-project) before your pull requests to the baseline repository will be merged. [Check here](https://community.oasis-open.org/s/searchdirectory?id=a233l0000038IIo) to see if your company has signed the ECLA.
 
@@ -64,9 +64,9 @@ The TSC shall determine the number of maintainers required to merge a contributi
 
 This document shall be ratified by the PGB before the public launch of the Baseline Protocol. Changes to this document shall require a simple majority of the PGB.
 
-### Details on OASIS and EEA Community Projects <a id="details-on-oasis-and-eea-community-projects"></a>
+### Details on OASIS and Ethereum OASIS Projects <a id="details-on-oasis-and-eea-community-projects"></a>
 
-Governance documents for [EEA Community Projects](https://github.com/ethereum-oasis-op/managed-open-project/blob/main/GOVERNANCE.md).
+Governance documents for [Ethereum OASIS Projects](https://github.com/ethereum-oasis-op/managed-open-project/blob/main/GOVERNANCE.md).
 
 ### TSC Rules for Mid-term Member Replacements <a id="replacements"></a>
 
diff --git a/docs/community/open-source-community/contributors.md b/docs/community/open-source-community/contributors.md
@@ -24,7 +24,7 @@ There is one other, important, way to contribute: **use the work in the Baseline
 
 The Baseline Protocol Code of Conduct is located here
 
-{% embed url="https://github.com/ethereum-oasis-op/baseline/blob/master/CODE_OF_CONDUCT.md" %}
+{% embed url="https://github.com/ethereum-oasis-op/baseline/blob/main/CODE_OF_CONDUCT.md" %}
 
 ## Technical Contributors <a href="#technical-contributors" id="technical-contributors"></a>
 
diff --git a/docs/deprecated-work/baseline-protocol-code/baseline-process.md b/docs/deprecated-work/baseline-protocol-code/baseline-process.md
@@ -41,7 +41,7 @@ To set up this business logic, use the Baseline Protocol Privacy Package [here](
 
 Once the business logic is rendered into provers, deploy the Workflow as follows:
 
-First deploy a Node that has the baseline protocol RPC interface implemented. The Nethermind Ethereum Client is the first to implement this code. Alternatively, you can deploy the [commit-mgr](https://github.com/ethereum-oasis-op/baseline/tree/master/examples/bri-2/commit-mgr) Ethereum client extension plus a client type of your choice (i.e. Besu, Infura, etc.)
+First deploy a Node that has the baseline protocol RPC interface implemented. The Nethermind Ethereum Client is the first to implement this code. Alternatively, you can deploy the [commit-mgr](https://github.com/ethereum-oasis-op/baseline/tree/main/examples/bri-2/commit-mgr) Ethereum client extension plus a client type of your choice (i.e. Besu, Infura, etc.)
 
 Next, use the `IBaselineRPC` call in the Client to deploy the Shield and Verifier contracts on-chain. This can be found [here](https://github.com/ethereum-oasis-op/baseline/tree/master/core/api).
 
diff --git a/docs/deprecated-work/baseline-protocol-code/packages/api.md b/docs/deprecated-work/baseline-protocol-code/packages/api.md
@@ -36,7 +36,7 @@ An initial set of JSON-RPC methods have been defined for inclusion in the specif
 #### Ethereum clients that support baseline JSON-RPC
 
 * [Nethermind](https://github.com/NethermindEth/nethermind) .NET client
-* Any client supported by the [commit-mgr](https://github.com/ethereum-oasis-op/baseline/tree/master/examples/bri-2/commit-mgr) service. These include:
+* Any client supported by the [commit-mgr](https://github.com/ethereum-oasis-op/baseline/tree/main/examples/bri-2/commit-mgr) service. These include:
   * [ganache](https://github.com/trufflesuite/ganache)
   * [besu](https://github.com/hyperledger/besu)
   * [Infura](https://infura.io/docs/ethereum)
diff --git a/docs/deprecated-work/baseline-protocol-code/packages/baseline.md b/docs/deprecated-work/baseline-protocol-code/packages/baseline.md
@@ -35,7 +35,7 @@ An initial set of JSON-RPC methods have been defined for inclusion in the specif
 #### Ethereum clients that support baseline JSON-RPC
 
 * [Nethermind](https://github.com/NethermindEth/nethermind) .NET client
-* Any client supported by the [commit-mgr](https://github.com/ethereum-oasis-op/baseline/tree/master/examples/bri-2/commit-mgr) service. These include:
+* Any client supported by the [commit-mgr](https://github.com/ethereum-oasis-op/baseline/tree/main/examples/bri-2/commit-mgr) service. These include:
   * [ganache](https://github.com/trufflesuite/ganache)
   * [besu](https://github.com/hyperledger/besu)
   * [Infura](https://infura.io/docs/ethereum)
diff --git a/docs/deprecated-work/bri/overview-of-reference-implementations.md b/docs/deprecated-work/bri/overview-of-reference-implementations.md
@@ -13,7 +13,7 @@ The baseline initiative's primary mission is to standardize these abstract techn
 
 Both the core libraries and the reference implementations should be thought of as a starting point for developers, a way of understanding the techniques and getting a jump start on their own work. So long as a developer follows the standard specifications of the baseline protocol, their work should interoperate with anyone else's implementation.
 
-If the core libraries and the reference implementations are just instances of the standard, why separate them into [core/](https://github.com/ethereum-oasis-op/baseline/tree/master/core) and different reference implementations (see [examples/](https://github.com/ethereum-oasis-op/baseline/tree/master/examples))? The answer is that the separation makes it easier to implement changes. The core should always be stable and capable of informing specifications development, where reference implementations are more "opinionated" and can constitute different approaches that utilize specific components, infrastructure, etc., while using the same core interfaces.
+If the core libraries and the reference implementations are just instances of the standard, why separate them into [core/](https://github.com/ethereum-oasis-op/baseline/tree/main/core) and different reference implementations (see [examples/](https://github.com/ethereum-oasis-op/baseline/tree/main/examples))? The answer is that the separation makes it easier to implement changes. The core should always be stable and capable of informing specifications development, where reference implementations are more "opinionated" and can constitute different approaches that utilize specific components, infrastructure, etc., while using the same core interfaces.
 
 > The core libraries are rails for standardization while reference implementations are rails for adoption.
 
@@ -43,9 +43,9 @@ Radish34 might be called BRI-0, but for historical purposes, and so as not to co
 
 ### **BRI-1**
 
-Baseline Reference Implementation #1 ([BRI-1](bri-1/)) was developed by contributors from Provide, Nethermind, EY and others, with support and oversight from the entire Baseline Maintainer team. This implementation correctly utilizes the core Baseline Protocol abstract interfaces, which are free of dependencies on any particular set of components or proprietary systems, but it also relies heavily on tools and systems made available by Provide. Provide's [Shuttle](https://shuttle.provide.services/waitlist) infrastructure deployment and manifold system is used by many \_baselining \_developers to make their work easier. Nethermind is the first Ethereum public client to implement the `IBaselineRPC` interface (found [here](https://github.com/ethereum-oasis-op/baseline/tree/master/core/api#interfaces)). NATS is a production-ready enterprise messaging layer that meets the privacy and performance requirements for baselining.
+Baseline Reference Implementation #1 ([BRI-1](bri-1/)) was developed by contributors from Provide, Nethermind, EY and others, with support and oversight from the entire Baseline Maintainer team. This implementation correctly utilizes the core Baseline Protocol abstract interfaces, which are free of dependencies on any particular set of components or proprietary systems, but it also relies heavily on tools and systems made available by Provide. Provide's [Shuttle](https://shuttle.provide.services/waitlist) infrastructure deployment and manifold system is used by many \_baselining \_developers to make their work easier. Nethermind is the first Ethereum public client to implement the [`IBaselineRPC` interface](https://github.com/ethereum-oasis-op/baseline/tree/master/core/api#interfaces)). NATS is a production-ready enterprise messaging layer that meets the privacy and performance requirements for baselining.
 
-Details on BRI-1 can be found [here](bri-1/), and the code can be found [here](https://github.com/ethereum-oasis-op/baseline/tree/master/examples/bri-1).
+Details on BRI-1 can be found [here](bri-1/), and the code can be found [here](https://github.com/ethereum-oasis-op/baseline/tree/main/examples/bri-1).
 
 ### **BRI-2**
 
diff --git a/docs/deprecated-work/bri/radish34/modifying-radish34.md b/docs/deprecated-work/bri/radish34/modifying-radish34.md
@@ -4,7 +4,7 @@ The Radish34 functional proof-of-concept \(POC\) demonstrates only a few key ste
 
 But what if you wanted to add tokenized inventory, shipping & logistics, invoicing, or trade finance functions like invoice factoring?
 
-As a POC, it is certainly true that the [code](https://github.com/ethereum-oasis-op/baseline/tree/master/examples/radish34) of Radish34 still needs to add a layer of abstraction to take it to the next level as production-capable code for supply chain applications. This would be a good place for community members to chip in, irrespective of the additional generalization effort of going from [POC to Protocol](from-poc-to-protocol.md).
+As a POC, it is certainly true that the [code](https://github.com/ethereum-oasis-op/baseline/tree/main/examples/radish34) of Radish34 still needs to add a layer of abstraction to take it to the next level as production-capable code for supply chain applications. This would be a good place for community members to chip in, irrespective of the additional generalization effort of going from [POC to Protocol](from-poc-to-protocol.md).
 
 An example of this is the code for the MSA, which you can find in the repo \[ here \]. Strictly speaking, the MSA is an instance of a Workflow [Step](https://docs.baseline-protocol.org/baseline-basics/glossary#workstep). A Workstep can implement a number of Tasks. The MSA implements, for example, a specialized zero knowledge circuit specially written to enforce the correctness of the business logic involved in calculating a PO’s correct volume discount. It also implements general [Tasks](https://docs.baseline-protocol.org/baseline-basics/glossary#task), such as messaging, digital signatures, and the process of generating, validating and storing the proof \(in this case, a state marker representing the rate table and the total number of units ordered\), and nullifying a previous proof when the state has changed.
 
diff --git a/docs/deprecated-work/bri/radish34/radish34-poc.md b/docs/deprecated-work/bri/radish34/radish34-poc.md
@@ -1,4 +1,4 @@
 # Radish34 POC
 
-If you’ve read the [Radish34 Explained](radish34-explained.md) section or played with the [user experience demo](radish34-interactive-demo.md) and now want to build and run the POC yourself, you’re in the right place. Find the authoritative set-up documentation in the Github repo [here](https://github.com/ethereum-oasis-op/baseline/tree/master/examples/radish34).
+If you’ve read the [Radish34 Explained](radish34-explained.md) section or played with the [user experience demo](radish34-interactive-demo.md) and now want to build and run the POC yourself, you’re in the right place. Find the authoritative set-up documentation in the Github repo [here](https://github.com/ethereum-oasis-op/baseline/tree/main/examples/radish34).
 
diff --git a/docs/deprecated-work/core/api/README.md b/docs/deprecated-work/core/api/README.md
@@ -105,5 +105,5 @@ deleteVaultSecret(vaultId: string, secretId: string): Promise<any>;
 The following providers of the Baseline API are available:
 
 - Ethers.js - *example provider; not yet implemented*
-- [Provide](https://provide.services) - enterprise-grade reference implementation (see [examples/bri-1/base-example](https://github.com/ethereum-oasis-op/baseline/tree/master/examples/bri-1/base-example))
+- [Provide](https://provide.services) - enterprise-grade reference implementation (see [examples/bri-1/base-example](https://github.com/ethereum-oasis-op/baseline/tree/main/examples/bri-1/base-example))
 - RPC - generic JSON-RPC provider
diff --git a/docs/governance/governance.md b/docs/governance/governance.md
@@ -14,7 +14,7 @@ In order to ensure clean IPR that allows the Baseline Protocol to remain an open
 
 ## Code of Conduct <a href="#code-of-conduct" id="code-of-conduct"></a>
 
-​Here is the link to the official [Code of Conduct](https://github.com/ethereum-oasis-op/baseline/blob/master/CODE\_OF\_CONDUCT.md).
+​Here is the official [Code of Conduct](https://github.com/ethereum-oasis-op/baseline/blob/main/CODE\_OF\_CONDUCT.md).
 
 ## **Charter: Baseline Open Source Project Governance** <a href="#charter-baseline-open-source-project-governance" id="charter-baseline-open-source-project-governance"></a>
 
diff --git a/docs/specs/README.md b/docs/specs/README.md
@@ -1,6 +1,6 @@
 # Baseline Protocol Specifications
 
-![Baseline Logo](https://raw.githubusercontent.com/ethereum-oasis-op/baseline/master/docs/assets/baseline-logo/Web/examples/PNGs/horizontal/baselineHorizontal-Logo-FullColor.png)
+![Baseline Logo](https://raw.githubusercontent.com/ethereum-oasis-op/baseline/main/docs/assets/baseline-logo/Web/examples/PNGs/horizontal/baselineHorizontal-Logo-FullColor.png)
 
 *Read the full documentation [here at docs.baseline-protocol.org](https://docs.baseline-protocol.org/).*
 *Join our [Slack workspace](https://communityinviter.com/apps/ethereum-baseline/join-us), [Discord channel](https://discord.com/invite/NE8AYD7), [Telegram channel](https://t.me/baselineprotocol) and follow us on [Twitter](https://twitter.com/baselineproto) for Baseline news and updates!* 
diff --git a/examples/deprecated/bri-1/lib/erp-connector-proxy/README.md b/examples/deprecated/bri-1/lib/erp-connector-proxy/README.md
@@ -1,4 +1,4 @@
-**⚠️ The "Baseline-SAP-Dynamics" demo is being integrated with [this new reference implementation](https://github.com/ethereum-oasis-op/baseline/tree/master/examples/shuttle-app) as a result of the `v0.1` release.**
+**⚠️ The "Baseline-SAP-Dynamics" demo is being integrated with [this new reference implementation](https://github.com/ethereum-oasis-op/baseline/tree/main/examples/shuttle-app) as a result of the `v0.1` release.**
 
 # Baselining Business Process Automation across SAP and Microsoft Dynamics
 
diff --git a/examples/deprecated/bri-1/lib/google-sheets-connector/README.md b/examples/deprecated/bri-1/lib/google-sheets-connector/README.md
@@ -1,4 +1,4 @@
-**⚠️ The "Baseline Mycrosoft Dynamics and Google Sheets" initiative is being integrated with [this new reference implementation](https://github.com/ethereum-oasis-op/baseline/tree/master/examples/shuttle-app) as a result of the `v0.1` release.**
+**⚠️ The "Baseline Mycrosoft Dynamics and Google Sheets" initiative is being integrated with [this new reference implementation](https://github.com/ethereum-oasis-op/baseline/tree/main/examples/shuttle-app) as a result of the `v0.1` release.**
 
 **🚀 The "Baseline Mycrosoft Dynamics and Google Sheets" source code can be found [here](https://github.com/ethereum-oasis-op/baseline/tree/init-core/examples/google-sheets-connector) on the `init-core` branch, as discussed above.**
 
diff --git a/examples/deprecated/bri-2/dashboard/components/Footers/FooterAdmin.js b/examples/deprecated/bri-2/dashboard/components/Footers/FooterAdmin.js
@@ -29,7 +29,7 @@ export default function FooterAdmin() {
             <ul className="flex flex-wrap list-none md:justify-end  justify-center">
               <li>
                 <a
-                  href="https://github.com/ethereum-oasis-op/baseline/blob/master/LICENSE"
+                    href="https://github.com/ethereum-oasis-op/baseline/blob/main/LICENSE.md"
                   className="text-black hover:text-gray-400 text-sm font-semibold block py-1 px-3"
                 >
                   CC0 License
diff --git a/examples/deprecated/bri-2/dashboard/components/Footers/FooterSmall.js b/examples/deprecated/bri-2/dashboard/components/Footers/FooterSmall.js
@@ -22,7 +22,7 @@ export default function FooterSmall(props) {
               <ul className="flex flex-wrap list-none md:justify-end  justify-center">
                 <li>
                   <a
-                    href="https://github.com/ethereum-oasis-op/baseline/blob/master/LICENSE"
+                    href="https://github.com/ethereum-oasis-op/baseline/blob/main/LICENSE.md"
                     className="text-black hover:text-gray-400 text-sm font-semibold block py-1 px-3"
                   >
                     CC0 License
diff --git a/examples/deprecated/radish34/README.md b/examples/deprecated/radish34/README.md

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`	`1`	`# Radish34 POC`
`2`	`2`
`3`		`-If you’ve read the [Radish34 Explained](radish34-explained.md) section or played with the [user experience demo](radish34-interactive-demo.md) and now want to build and run the POC yourself, you’re in the right place. Find the authoritative set-up documentation in the Github repo [here](https://github.com/ethereum-oasis-op/baseline/tree/master/examples/radish34).`
	`3`	`+If you’ve read the [Radish34 Explained](radish34-explained.md) section or played with the [user experience demo](radish34-interactive-demo.md) and now want to build and run the POC yourself, you’re in the right place. Find the authoritative set-up documentation in the Github repo [here](https://github.com/ethereum-oasis-op/baseline/tree/main/examples/radish34).`
`4`	`4`