Merge pull request #1345 from blockchaindevsh/fix_link

fix link

Author: krofax

pages/stack/fault-proofs/cannon.mdx

@@ -25,7 +25,7 @@ Now for simplicity, when referring to Cannon in this documentation, we are refer
 
 ## Control flow
 
-![Fault Proof Control Flow.](/img/op-stack/protocol/fault-proof-control-flow.svg)
+![Fault Proof Control Flow.](/public/img/op-stack/protocol/fault-proof-control-flow.svg)
 
 In the above diagram, recreated from the [OP Fault Proof System video](https://www.youtube.com/watch?v=nIN5sNc6nQM) by Clabby, we can see
 that Cannon interacts with OP-Challenger and OP-Program. However, this diagram is a simplification of the relationship between
@@ -61,7 +61,7 @@ Now, we will go over each major component that makes up Cannon. Components are g
 Cannon, and may be correlated to one or more Go files. For brevity, each Go file will be explained at a high level, with the
 most important features / considerations highlighted.
 
-![Cannon Components Overview.](/img/op-stack/protocol/cannon-internal-overview.svg)
+![Cannon Components Overview.](/public/img/op-stack/protocol/cannon-internal-overview.svg)
 
 ### `mipsevm` state and memory