WIP (needs to be pushed to test)

docs/op-stack/src/.vuepress/config.js

@@ -9,7 +9,7 @@ module.exports = {
     ['meta', { name: 'theme-color', content: '#3eaf7c' }],
     ['meta', { name: 'apple-mobile-web-app-capable', content: 'yes' }],
     ['meta', { name: 'apple-mobile-web-app-status-bar-style', content: 'black' }],
-    ['meta', { name: 'twitter:image', content: 'https://stack.optimism.io/assets/logos/logo.png' }],
+    ['meta', { name: 'og:image', content: 'https://stack.optimism.io/assets/logos/logo.png' }],
     ['link', { rel: "icon", type: "image/png", sizes: "32x32", href: "/assets/logos/favicon.png"}],
   ],
   theme: path.resolve(__dirname, './theme'),

docs/op-stack/src/docs/releases/README.md

@@ -3,16 +3,16 @@ title: Release History
 lang: en-US
 ---
 
-The OP Stack is a decentralized development stack maintained by the Optimism Collective and built to power Optimism. 
-The OP Stack is constantly evolving as new layers and modules are developed. The OP Stack is also not a product (in the traditional sense) but rather a collection of software components that power the Optimism ecosystem.
+The OP Stack codebase is a decentralized development stack maintained by the Optimism Collective and built to power Optimism. 
+The OP Stack is constantly evolving as new layers and modules are developed. The OP Stack codebase is also not a product (in the traditional sense) but rather a collection of software components that power the Optimism ecosystem.
 
-**A “Release” of the OP Stack is a particular set of software components that are production-ready and which fit the stack’s design principles and goals.**
+**A “Release” of the OP Stack codebase is a particular set of software components that are production-ready and which fit the stack’s design principles and goals.**
 
-Only the software components included within the Current Release of the OP Stack are considered in the scope of the OP Stack. Any usage of the OP Stack outside of the official, intended capabilities of the Current Release are considered [OP Stack Hacks](../build/hacks.md) — unofficial modifications that are useful for experimentation but could have unforeseen results, such as security vulnerabilities, and are likely cause your chain to no longer be interoperable with the Optimism Superchain (link). **Developer support for OP Stack Hacks is limited — when in doubt, stick to the capabilities of the Current Release!**
+Only the software components included within the Current Release of the OP Stack codebase are considered in the scope of the OP Stack. Any usage of the OP Stack outside of the official, intended capabilities of the Current Release are considered [OP Stack Hacks](../build/hacks.md) — unofficial modifications that are useful for experimentation but could have unforeseen results, such as security vulnerabilities, and are likely cause your chain to no longer be interoperable with the Optimism Superchain (link). **Developer support for OP Stack Hacks is limited — when in doubt, stick to the capabilities of the Current Release!**
 
 ## Current Release
 
-[OP Stack V1: Bedrock](./bedrock/)
+[OP Stack codebase V1: Bedrock](./bedrock/)
 
 ## Past Releases
 

docs/op-stack/src/docs/releases/bedrock/README.md

 ---
-title: OP Stack V1 - Bedrock
+title: OP Stack codebase V1 - Bedrock
 lang: en-US
 ---
 
 ## Overview
 
-The first release of the OP Stack is called **Bedrock**. 
+The first release of the OP Stack codebase is called **Bedrock**. 
 The Bedrock release primarily consists of the core software required to run L2 blockchains and was originally designed to power an upgrade to the Optimism Mainnet network.
 
 ## Resources

docs/op-stack/src/docs/releases/bedrock/differences.md

@@ -4,7 +4,7 @@ lang: en-US
 ---
 
 It's important to note that there are various minor discrepancies between the behavior of Optimism and Ethereum.
-You should be aware of these descrepancies when building apps on top of Optimism or the OP Stack
+You should be aware of these descrepancies when building apps on top of Optimism or the OP Stack codebase.
 
 ## Opcode Differences
 
@@ -125,7 +125,7 @@ There are several differences in the way blocks are produced between L1 Ethereum
 
 ### JSON-RPC differences
 
-OP Stack uses the same [JSON-RPC API](https://eth.wiki/json-rpc/API) as Ethereum.
+OP Stack codebase uses the same [JSON-RPC API](https://eth.wiki/json-rpc/API) as Ethereum.
 Some additional OP Stack specific methods have been introduced.
 See the full list of [custom JSON-RPC methods](https://community.optimism.io/docs/developers/build/json-rpc/) for more information.
 

docs/op-stack/src/docs/releases/bedrock/explainer.md

@@ -8,7 +8,7 @@ meta:
 
 ![Bedrock](https://dev.optimism.io/content/images/size/w2000/2022/12/bedrock-BLUE.jpg)
 
-Bedrock is the name of the first ever official release of the OP Stack, which is a set of free and open-source modular components that work together to power Optimism.
+Bedrock is the name of the first ever official release of the OP Stack codebase, which is a set of free and open-source modular components that work together to power Optimism.
 
 - To understand what is in the Bedrock release, keep reading.
 - To develop on Optimism Mainnet, which will upgrade its infrastructure to the Bedrock release, read the docs.
@@ -55,7 +55,7 @@ Bedrock was built to be modular & upgradeable, to reuse existing code from Ether
 
 ### Modularity
 
-Bedrock makes it easy to swap out different components in the OP Stack and add new capabilities by using well-defined interfaces and versioning schemes. This allows for a flexible architecture that can adapt to future developments in the Ethereum ecosystem.
+Bedrock makes it easy to swap out different components in the OP Stack codebase and add new capabilities by using well-defined interfaces and versioning schemes. This allows for a flexible architecture that can adapt to future developments in the Ethereum ecosystem.
 
 Examples:
 - Separation of [rollup node](#rollup-node) and execution client
@@ -192,13 +192,13 @@ After a sequencer processes one or more L2 blocks, the outputs computed from exe
 
 In Bedrock, outputs are hashed in a tree-structured form which minimizes the cost of proving any piece of data captured by the outputs. Proposers periodically submit **output roots** that are Merkle roots of the entire [canonical L2 chain](#protocol) to the L1.
 
-Future upgrades of the OP Stack should include a specification for a variation of a fault proof with bonding included to create incentives for proposers to propose correct output roots.
+Future upgrades of the OP Stack codebase should include a specification for a variation of a fault proof with bonding included to create incentives for proposers to propose correct output roots.
 
 For full details, read the [L2 Output Root Proposals section](https://github.com/ethereum-optimism/optimism/blob/develop/specs/proposals.md#l2-output-root-proposals-specification) of the protocol specifications.
 
 ## Implementation
 
-With Bedrock, the OP Stack leans heavily into the technical separation of concerns specified by Ethereum by mirroring the separation between the Ethereum execution layer and consensus layer. Bedrock introduces separation of execution client and rollup node in this same way.
+With Bedrock, the OP Stack codebase leans heavily into the technical separation of concerns specified by Ethereum by mirroring the separation between the Ethereum execution layer and consensus layer. Bedrock introduces separation of execution client and rollup node in this same way.
 
 ### Execution Client
 
@@ -281,7 +281,7 @@ Although fault proof construction and verification is implemented in the [Cannon
 
 ### Protocol Specification
 
-The protocol specification defines the technical details of the OP Stack. It is the most up-to-date source of truth for the inner workings of the protocol. The protocol specification is located in the ethereum-optimism [monorepo](https://github.com/ethereum-optimism/optimism/blob/develop/specs/README.md).
+The protocol specification defines the technical details of the OP Stack codebase. It is the most up-to-date source of truth for the inner workings of the protocol. The protocol specification is located in the ethereum-optimism [monorepo](https://github.com/ethereum-optimism/optimism/blob/develop/specs/README.md).
 
 ### Bedrock Differences