Commit e8de7b19 authored by Cypher Pepe's avatar Cypher Pepe Committed by GitHub

chore: Fix Typos and Minor Edits in Documentation Files* (#12881)

* typo corr 2022-02-02-inflation-vuln.md

* typo corr README.md

* typo corr RUNBOOK.md
parent 3e7c1dd6
...@@ -58,7 +58,7 @@ timeline and activities were as follows: ...@@ -58,7 +58,7 @@ timeline and activities were as follows:
(Using github handles as identifiers) (Using github handles as identifiers)
- 2022-02-02 1625: smartcontracts receives an e-mail from saurik claiming to have found a critical - 2022-02-02 1625: smartcontracts receives an e-mail from saurik claiming to have found a critical
issue in L2Geth. E-mail was sent to securityoptimism.io. issue in L2Geth. E-mail was sent to security@optimism.io.
- 2022-02-02 X: saurik messaged smartcontracts on Discord to make sure we checked the e-mail since - 2022-02-02 X: saurik messaged smartcontracts on Discord to make sure we checked the e-mail since
he knew we had a prior problem where security advisories went to spam. he knew we had a prior problem where security advisories went to spam.
- 2022-02-02 1650: Huddle begins in #security on Slack. - 2022-02-02 1650: Huddle begins in #security on Slack.
......
# op-challenger # op-challenger
The `op-challenger` is a modular **op-stack** challenge agent written in The `op-challenger` is a modular **op-stack** challenge agent written in
golang for dispute games including, but not limited to,attestation games, golang for dispute games including, but not limited to, attestation games,
fault games, and validity games. To learn more about dispute games, visit fault games, and validity games. To learn more about dispute games, visit
the [fault proof specs][proof-specs]. the [fault proof specs][proof-specs].
......
...@@ -28,7 +28,7 @@ OP_CONDUCTOR_NODE_RPC=<node-rpc-endpoint> # for example, http://op-node:8545 ...@@ -28,7 +28,7 @@ OP_CONDUCTOR_NODE_RPC=<node-rpc-endpoint> # for example, http://op-node:8545
OP_CONDUCTOR_EXECUTION_RPC=<execution-rpc-endpoint> # for example, http://op-geth:8545 OP_CONDUCTOR_EXECUTION_RPC=<execution-rpc-endpoint> # for example, http://op-geth:8545
OP_CONDUCTOR_NETWORK=<network-name> # for example, base-mainnet, op-mainnet, etc, should be same as OP_NODE_NETWORK OP_CONDUCTOR_NETWORK=<network-name> # for example, base-mainnet, op-mainnet, etc, should be same as OP_NODE_NETWORK
OP_CONDUCTOR_HEALTHCHECK_INTERVAL=<healthcheck-interval> # in seconds OP_CONDUCTOR_HEALTHCHECK_INTERVAL=<healthcheck-interval> # in seconds
OP_CONDUCTOR_HEALTHCHECK_UNSAFE_INTERVAL=<unsafe-interval> # Interval allowed between unsafe head and now measured in seconds in seconds OP_CONDUCTOR_HEALTHCHECK_UNSAFE_INTERVAL=<unsafe-interval> # Interval allowed between unsafe head and now measured in seconds
OP_CONDUCTOR_HEALTHCHECK_MIN_PEER_COUNT=<min-peer-count> # minimum number of peers required to be considered healthy OP_CONDUCTOR_HEALTHCHECK_MIN_PEER_COUNT=<min-peer-count> # minimum number of peers required to be considered healthy
OP_CONDUCTOR_RAFT_BOOTSTRAP=true/false # set to true if you want to bootstrap the raft cluster OP_CONDUCTOR_RAFT_BOOTSTRAP=true/false # set to true if you want to bootstrap the raft cluster
``` ```
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment