Skip to content

Commit e6a731c

Browse files
authored
Merge pull request #1694 from ethereum-optimism/fix-images
Fix images links
2 parents 4c1c33d + d3d8def commit e6a731c

File tree

3 files changed

+4
-4
lines changed

3 files changed

+4
-4
lines changed

pages/operators/chain-operators/tools/op-conductor.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ The design of the `op-conductor` provides the following guarantees:
5050

5151
## Design
5252

53-
![op-conductor.](/img/operators/chain-operators/op-conductor.svg)
53+
![op-conductor.](/img/builders/chain-operators/op-conductor.svg)
5454

5555
**On a high level, `op-conductor` serves the following functions:**
5656

pages/stack/fault-proofs/cannon.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -35,9 +35,9 @@ Additionally, we will explore the differences between Cannon and the onchain `MI
3535
implementation, please refer to [MIPS reference](mips).
3636
Now for simplicity, when referring to Cannon in this documentation, we are referring to the offchain implementation.
3737

38-
## Control flow
38+
## Control flow
3939

40-
![Fault Proof Control Flow.](/public/img/op-stack/protocol/fault-proof-control-flow.svg)
40+
![Fault Proof Control Flow.](/img/op-stack/protocol/fault-proof-control-flow.svg)
4141

4242
In the above diagram, recreated from the [OP Fault Proof System video](https://www.youtube.com/watch?v=nIN5sNc6nQM) by Clabby, we can see
4343
that Cannon interacts with OP-Challenger and OP-Program. However, this diagram is a simplification of the relationship between

pages/superchain/superchain-explainer.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ import { Callout } from 'nextra/components'
2828
Superchain interop enables trust-minimized, low-latency, cross-chain composability. Superchain interop is in active development and is available for testing. [Learn more about Superchain Interop](https://docs.optimism.io/interop/explainer).
2929
</Callout>
3030

31-
The next major scalability improvement to the OP Stack after Bedrock is to introduce the concept of *a Superchain*: a network of chains that share bridging, decentralized governance, upgrades, a communication layer and moreall built on the OP Stack.
31+
The next major scalability improvement to the OP Stack after Bedrock is to introduce the concept of *a Superchain*: a network of chains that share bridging, decentralized governance, upgrades, a communication layer and more, all built on the OP Stack.
3232

3333
The launch of the Superchain would merge OP Mainnet and other chains into a single unified network of OP Chains (i.e., chains within the Superchain), and mark a major step towards bringing scalable and decentralized compute to the world. The goal of this document is to describe the scalability vision, the Superchain concept, and some changes to the OP Stack required to make this vision a reality.
3434

0 commit comments

Comments
 (0)