part 1 lang updates

lang updates part 1
zhiqiangxu · Dec 11, 2023 · 6167e49 · 6167e49
1 parent d61370b
commit 6167e49
Show file tree

Hide file tree

Showing 7 changed files with 10 additions and 11 deletions.
diff --git a/pages/builders/chain-operators/overview.mdx b/pages/builders/chain-operators/overview.mdx
@@ -27,8 +27,8 @@ OP Stack chains require four different components for deployment. It's useful to
 <Callout type="info">
   Client Implementations
 
-  *   Consensus clients: `op-node` (maintained by OP Labs) and [`magi`](https://github.com/a16z/magi) (maintained by a16z)
-  *   Execution clients: `op-geth` (maintained by OP Labs), [`op-erigon`](https://github.com/testinprod-io/op-erigon) (maintained by Test in Prod), and `op-nethermind` (coming soon)
+  *   Consensus clients: `op-node` (maintained by Optimism) and [`magi`](https://github.com/a16z/magi) (maintained by a16z)
+  *   Execution clients: `op-geth` (maintained by Optimism), [`op-erigon`](https://github.com/testinprod-io/op-erigon) (maintained by Test in Prod), and `op-nethermind` (coming soon)
 </Callout>
 
 ## Chain Operator Tutorials

diff --git a/pages/builders/chain-operators/tutorials/create-l2-rollup.mdx b/pages/builders/chain-operators/tutorials/create-l2-rollup.mdx
@@ -47,14 +47,14 @@ You can also run additional non-Sequencer nodes if you'd like (not included in t
 
 OP Stack nodes, like Ethereum nodes, have a consensus client.
 The consensus client is responsible for determining the list and ordering of blocks and transactions that are part of your blockchain.
-Several implementations of the OP Stack consensus client exist, including `op-node` (maintained by OP Labs) and [`magi`](https://github.com/a16z/magi) (maintained by a16z).
+Several implementations of the OP Stack consensus client exist, including `op-node` (maintained by Optimism) and [`magi`](https://github.com/a16z/magi) (maintained by a16z).
 In this tutorial we'll be using the [`op-node` implementation](https://github.com/ethereum-optimism/optimism/tree/develop/op-node) found within the [Optimism Monorepo](https://github.com/ethereum-optimism/optimism).
 
 #### Execution Client
 
 OP Stack nodes, like Ethereum nodes, also have an execution client.
 The execution client is responsible for executing transactions and storing/updating the state of the blockchain.
-Various implementations of the OP Stack execution client exist, including `op-geth` (maintained by OP Labs), [`op-erigon`](https://github.com/testinprod-io/op-erigon) (maintained by Test in Prod), and `op-nethermind` (coming soon).
+Various implementations of the OP Stack execution client exist, including `op-geth` (maintained by Optimism), [`op-erigon`](https://github.com/testinprod-io/op-erigon) (maintained by Test in Prod), and `op-nethermind` (coming soon).
 In this tutorial we'll be using the [`op-geth` implementation](https://github.com/ethereum-optimism/op-geth) found within the [`op-geth` repository](https://github.com/ethereum-optimism/op-geth).
 
 ### Batcher

diff --git a/pages/builders/tools/faucets.mdx b/pages/builders/tools/faucets.mdx
@@ -20,7 +20,7 @@ Faucets can occasionally also run out of ETH, so if you're having trouble gettin
 
 ## Superchain Faucet
 
-The [Superchain Faucet](https://app.optimism.io/faucet?utm_source=docs) is a developer tool hosted by OP Labs that allows developers to get free testnet ETH to test apps on testnet OP Chains like Base Sepolia, OP Sepolia, PGN Sepolia, Zora Sepolia, and other OP Chains in the Superchain.
+The [Superchain Faucet](https://app.optimism.io/faucet?utm_source=docs) is a developer tool hosted by Optimism that allows developers to get free testnet ETH to test apps on testnet OP Chains like Base Sepolia, OP Sepolia, PGN Sepolia, Zora Sepolia, and other OP Chains in the Superchain.
 The Superchain Faucet is a great place to start if you're looking for testnet ETH.
 
 ## Additional Faucets

diff --git a/pages/connect/contribute/docs-contribute.mdx b/pages/connect/contribute/docs-contribute.mdx
@@ -62,7 +62,6 @@ Decisions about individual PRs, tutorials, and major docs updates are made by th
 We want to transition to a more community-informed and community-generated approach for the Optimism Developer Docs, so please raise questions in issues, submit PRs, or contact the team:
 
 *   [[email protected]](mailto:[email protected])
-*   [@OPLabsPBC](https://twitter.com/OPLabsPBC)
 *   [developer support channel](https://github.com/ethereum-optimism/developers/)
 
 ### A note on plagiarism

diff --git a/pages/connect/contribute/style-guide.mdx b/pages/connect/contribute/style-guide.mdx
@@ -470,7 +470,7 @@ Please use `*` instead of `-` for items in a list. This maintains consistency ac
 
 *   Spell out acronyms the first time used on any given page. Then, abbreviate in parentheses afterward. Link users to the glossary, when applicable.
 
-    **Example**: `Know Your Customer (KYC)`
+    **Example**: `Externally Owned Account (EOA)`
 
 ### Punctuation
 

diff --git a/pages/connect/resources/security-policy.mdx b/pages/connect/resources/security-policy.mdx
@@ -37,15 +37,15 @@ If you think you have found a significant bug or vulnerabilities in OP Stack sma
 
 ## Reporting Other Vulnerabilities
 
-For vulnerabilities in any websites, email servers, or other non-critical infrastructure within the OP Stack, please email [OP Labs](https://www.oplabs.co/) at [[email protected]](mailto:[email protected]) and include detailed instructions for confirming and reproducing the vulnerability.
+For vulnerabilities in any websites, email servers, or other non-critical infrastructure within the OP Stack, please email [[email protected]](mailto:[email protected]) and include detailed instructions for confirming and reproducing the vulnerability.
 
 ### Vulnerability Disclosure
 
-Each OP Stack component maintainer may determine its own process for vulnerability disclosure. However, the following describes a recommended process for disclosure that is currently in use by [OP Labs](https://www.oplabs.co/).
+Each OP Stack component maintainer may determine its own process for vulnerability disclosure. However, the following describes a recommended process for disclosure that is currently in use by the Foundation’s service provider, [OP Labs](https://www.oplabs.co/).
 
 In the event that an OP Stack component maintainer learns of a critical security vulnerability, the maintainer reserves the right to silently fix it without immediately publicly disclosing the existence or nature of the vulnerability.
 
-In such a scenario, the disclosure process used by [OP Labs](https://www.oplabs.co/) is as follows:
+In such a scenario, the disclosure process used by the Foundation’s service provider, [OP Labs](https://www.oplabs.co/), is as follows:
 
 1.  Silently fix the vulnerability and include the fix in release X.
 2.  After 4-8 weeks, disclose that release X contained a security fix.

diff --git a/theme.config.tsx b/theme.config.tsx
@@ -19,7 +19,7 @@ const config: DocsThemeConfig = {
     link: 'https://github.com/ethereum-optimism/docs',
   },
   chat: {
-    link: 'https://twitter.com/OPLabsPBC',
+    link: 'https://twitter.com/OptimismGov',
     icon: (
       <svg width="24" height="24" viewBox="0 0 248 204">
         <path