Update BalancerMaxis → balancer org in GitHub URLs

docs/.vuepress/components/PermissionTable.vue

@@ -166,10 +166,10 @@ export default defineComponent({
         const [permissionsRes, reverseAddressRes, actionIdsRes] =
           await Promise.all([
             fetch(
-              `https://raw.githubusercontent.com/BalancerMaxis/bal_addresses/main/outputs/permissions/active/${this.chain}.json`
+              `https://raw.githubusercontent.com/balancer/bal_addresses/main/outputs/permissions/active/${this.chain}.json`
             ),
             fetch(
-              `https://raw.githubusercontent.com/BalancerMaxis/bal_addresses/main/outputs/${this.chain}_reverse.json`
+              `https://raw.githubusercontent.com/balancer/bal_addresses/main/outputs/${this.chain}_reverse.json`
             ),
             fetch(
               `https://raw.githubusercontent.com/balancer/balancer-deployments/master/action-ids/${this.chain}/action-ids.json`

docs/concepts/governance/multisig.md

@@ -55,13 +55,13 @@ Further, fee collection and processing requires tokens to be swept from the vaul
 
 All Balancer Multisigs are deployed using [Gnosis Safe](https://gnosis-safe.io/), the most battle-tested Multisig contract on Ethereum. The DAO and Treasury Multisigs with the ability to change protocol operations or access to treasury funds are require 6-of-11 singers to process transactions. The signer structure of the Multisigs may change if voted on through the governance process.
 
-Over time, various functions have been delegated to different Multisigs. The Balancer Maxis working group is responsible for ensuring the application of governance on chain. The [Balancer Multisig Ops Repo](https://github.com/BalancerMaxis/Multisig-ops) describes all Multisigs and operations as well as the external touch-points available.
+Over time, various functions have been delegated to different Multisigs. The Balancer Maxis working group is responsible for ensuring the application of governance on chain. The [Balancer Multisig Ops Repo](https://github.com/balancer/Multisig-ops) describes all Multisigs and operations as well as the external touch-points available.
 
 ## The Signers
 
 Balancer’s Multisig signers are a diverse set of widely respected community members. These are the current signers as of February 2023:
 
-**Note that the list below was last updated in February 2023. The Maxis keep an up-to-date list of their signers and Multisigs [here](https://github.com/BalancerMaxis/Multisig-ops)**
+**Note that the list below was last updated in February 2023. The Maxis keep an up-to-date list of their signers and Multisigs [here](https://github.com/balancer/Multisig-ops)**
 
 ### DAO Multisig Signer Set
 

docs/concepts/governance/process.md

@@ -4,7 +4,7 @@
 
 The Balancer Governance process has evolved through a number of BIPs as balancer moves along on it's quest towards decentralization. The most recent governance overhaul BIP at the time of this writing is [BIP-163](https://snapshot.org/#/balancer.eth/proposal/0xcd2cab0522b0e9a90ad40f93aca4505b17d60468224c22b69c4f9bd2bbd64e31).
 
-Balancer governance submissions consist of 2 items, an English proposal and a multisig payload that executes the changes described onchain. The Balancer Maxis, who can be found on the [Balancer Discord](https://discord.balancer.fi/) or contacted through an issue in the [Balancer Multisig Ops Repo](https://github.com/BalancerMaxis/multisig-ops/issues) are tasked with supporting community members in putting together proposals when required, and with the final evaluation and execution of approved proposals. Below are more details on the governance process as of BIP-163.
+Balancer governance submissions consist of 2 items, an English proposal and a multisig payload that executes the changes described onchain. The Balancer Maxis, who can be found on the [Balancer Discord](https://discord.balancer.fi/) or contacted through an issue in the [Balancer Multisig Ops Repo](https://github.com/balancer/multisig-ops/issues) are tasked with supporting community members in putting together proposals when required, and with the final evaluation and execution of approved proposals. Below are more details on the governance process as of BIP-163.
 
 ![img.png](./images/govProcess.png)
 
@@ -67,9 +67,9 @@ Further, votes requesting new gauges should include the following information:
 
 A Pull Request(PR) that posts a transaction to a gnosis safe multisig which executes the changes specified by the BIP onchain is required as part of the body of a Proposal specified above before it can be brought to valid snapshot.
 
-The file(s) should be added into their own directory here on the [Multisig Ops Repo](https://github.com/BalancerMaxis/multisig-ops/tree/main/BIPs/00proposed). Once the BIP is ready to go to Snapshot vote and a BIP number is selected, the files will be moved into the [BIPs directory](https://github.com/BalancerMaxis/multisig-ops/tree/main/BIPs) following the apparent pattern there. The description of the pull request should contain a link to the Forum Post with the English Specification of it. The Balancer Maxis will review the payload and post any concerns or questions in review.
+The file(s) should be added into their own directory here on the [Multisig Ops Repo](https://github.com/balancer/multisig-ops/tree/main/BIPs/00proposed). Once the BIP is ready to go to Snapshot vote and a BIP number is selected, the files will be moved into the [BIPs directory](https://github.com/balancer/multisig-ops/tree/main/BIPs) following the apparent pattern there. The description of the pull request should contain a link to the Forum Post with the English Specification of it. The Balancer Maxis will review the payload and post any concerns or questions in review.
 
-Examples of how to submit payload PRs for common governance quests can be found [HERE](https://github.com/BalancerMaxis/multisig-ops/tree/main/BIPs/00examples)
+Examples of how to submit payload PRs for common governance quests can be found [HERE](https://github.com/balancer/multisig-ops/tree/main/BIPs/00examples)
 
 ### **Step 4: Snapshot**
 
@@ -93,7 +93,7 @@ If a Snapshot is approved by governance but rejected for technical reasons, the
 
 If the vote fails in an approve/reject vote it will not be executed on. Proposes are encouraged to wait at least 30 days and/or until something significant has changed before posting another vote, and delegates with sufficient veBAL to post votes are asked to be considerate about creating governance noise and SPAM by reposting failed votes in rapid succession.
 
-If the vote succeeds or a result has been chosen, follow through to make sure that it is properly executed. Depending on what the vote is about, it may require an action by the [multisig](./multisig.md). The Balancer Maxis are currently responsible for organizing the onchain execution of governance and are working toward making their process as transparent as possible in the public [Balancer Multisig Ops Github Repo](https://github.com/BalancerMaxis/multisig-ops)
+If the vote succeeds or a result has been chosen, follow through to make sure that it is properly executed. Depending on what the vote is about, it may require an action by the [multisig](./multisig.md). The Balancer Maxis are currently responsible for organizing the onchain execution of governance and are working toward making their process as transparent as possible in the public [Balancer Multisig Ops Github Repo](https://github.com/balancer/multisig-ops)
 
 Assuming all reviews are finished and dependencies are met, the Maxis will make every effort to execute on finished in the same week that governance concludes. Note that it some cases complex BIPs may require more time for final multisigner review.