Fix grammar

.github/styles/config/vocabularies/default/accept.txt

@@ -154,6 +154,7 @@ PGN
 Pimlico
 Polis
 Protocol Kit
+Protofire
 PublicMint
 README
 REI

pages/advanced/api-new-networks.md

@@ -1,6 +1,6 @@
 ## New Supported Chains
 
-Safe's vision is to make every account in Web3 a smart account. Therefore, we prioritise teams and chains building with smart accounts, especially if they push account abstraction (e.g. ERC-4337/EIP-1271 adoption) with Safe (learn more [here](https://docs.safe.global/home/4337-safe)).
+Safe's vision is to make every Web3 account a smart account. Therefore, we prioritize teams and chains building with smart accounts, especially if they push account abstraction (for example, ERC-4337/EIP-1271 adoption) with Safe (learn more [here](https://docs.safe.global/home/4337-safe)).
 
 To have the full Safe stack running on your chain network. You need to consider each of these steps:
 
@@ -13,31 +13,31 @@ To have the full Safe stack running on your chain network. You need to consider
 
 **Cost**
 
-The contracts are fully open source, but there is gas needed in the native currency of the new chain for the contracts deployment.
+The contracts are fully open source, but gas is needed in the native currency of the new chain for contract deployment.
 
 **Timeline**
 
-Pull Requests on Safe's GitHub are reviewed roughly on a two week cadence.
+Pull Requests on Safe's GitHub are reviewed roughly on a two-week cadence.
 
 **EVM only**
 
-Safe's security is based on the contracts deployed in EVM compatible networks. For the time being, we are not looking to extend beyond EVM.
+Safe's security is based on the contracts deployed in EVM-compatible networks. For the time being, we are not looking to extend beyond EVM.
 
-### Safe{Wallet} iterface and Safe{Core} infrastructure
+### Safe{Wallet} interface and Safe{Core} infrastructure
 
 **Process**
 
-- You will need a dedicated team to run Safe's front-end and back-end services. There are two options, to pursue native or forked support:
-  - Native integration ([app.safe.global](https://app.safe.global)): Safe team
+- You will need a dedicated team to run Safe's front-end and back-end services. Two options are available:
+  - Native integration ([app.safe.global](https://app.safe.global)): Supported by the Safe team
     - Fill out this form: https://noteforms.com/forms/request-safe-ui-and-infra-support-4weugt
-    - The Safe team evaluates additional chains that need Wallet/Core support every quarter, based on a priority matrix. 
-  - Forked integration: Can be run by the chain itself or via an ecosystem third party like [Protofire](https://protofire.io) or [Den](https://www.onchainden.com).
+    - The Safe team evaluates additional chains that need Wallet/Core support every quarter based on a priority matrix. 
+  - Forked integration: Can be run by the new chain itself or via an ecosystem third party like [Protofire](https://protofire.io) or [Den](https://www.onchainden.com).
 - Enter into agreement with your chosen provider.
 
 **Cost**
 
-- Safe is fully open source, but requires someone to run and maintain the [web interface](https://github.com/safe-global/safe-wallet-web) and [infrastructure](https://github.com/safe-global/safe-infrastructure/blob/main/docs/running_production.md)
-- If run by any third party (including Safe) cost is based on an individual agreement.
+- Safe is fully open source but requires someone to run and maintain the [web interface](https://github.com/safe-global/safe-wallet-web) and [infrastructure](https://github.com/safe-global/safe-infrastructure/blob/main/docs/running_production.md)
+- Cost is based on an individual agreement if run by any third party (including Safe).
 - Primary cost factors:
   - Deployment costs.
   - Indexing.
@@ -46,4 +46,4 @@ Safe's security is based on the contracts deployed in EVM compatible networks. F
 **Timeline**
 
 - Based on individual agreement
-- Prioritisation for native integration ([app.safe.global](https://app.safe.global)) is primarily based on the network's smart account/account abstraction strategy (e.g. is every user account a Safe under the hood beyond the usage of Safe as a multi-signature for treasury management?) and [additional gathered metrics](https://noteforms.com/forms/request-safe-ui-and-infra-support-4weugt).
+- Prioritisation for native integration ([app.safe.global](https://app.safe.global)) is primarily based on the network's smart account/account abstraction strategy (for example: is every user account a Safe under the hood beyond the usage of Safe as a multi-signature for treasury management?) and [additional gathered metrics](https://noteforms.com/forms/request-safe-ui-and-infra-support-4weugt).