Round up of a few typo fixes (#15383)

* Fix link to OPCM

* Fix typo.

* Fix Withdrawals spelling

* Fix method name in comment

Author: ajsutton

.circleci/config.yml

@@ -433,7 +433,7 @@ jobs:
         type: boolean
         default: false
       resource_class:
-        description: Docker resoruce class
+        description: Docker resource class
         type: string
         default: medium
     machine:

op-e2e/actions/proofs/isthmus_fork_test.go

@@ -108,24 +108,24 @@ func testIsthmusActivationAtGenesis(gt *testing.T, testCfg *helpers.TestCfg[any]
 	env.RunFaultProofProgramFromGenesis(t, safeBlock.Number, testCfg.CheckResult, testCfg.InputParams...)
 }
 
-// Test_ProgramAction_IsthmusWithdrawlsRoot tests the withdrawals root in the header:
+// Test_ProgramAction_IsthmusWithdrawalsRoot tests the withdrawals root in the header:
 // - post canyon but pre Isthmus
 // - post Isthmus
 // We do not include pre canyon behaviour (nil withdrawals root) since Canyon does not support Cancun L1.
 // It does this by activating the relevant forks at genesis.
 // It runs the fault proof program.
-func Test_ProgramAction_IsthmusWithdrawlsRoot(gt *testing.T) {
+func Test_ProgramAction_IsthmusWithdrawalsRoot(gt *testing.T) {
 	matrix := helpers.NewMatrix[any]()
 
 	matrix.AddDefaultTestCases(
 		nil,
 		helpers.NewForkMatrix(helpers.Holocene, helpers.Isthmus),
-		testWithdrawlsRoot,
+		testWithdrawalsRoot,
 	)
 
 	matrix.Run(gt)
 }
-func testWithdrawlsRoot(gt *testing.T, testCfg *helpers.TestCfg[any]) {
+func testWithdrawalsRoot(gt *testing.T, testCfg *helpers.TestCfg[any]) {
 	t := actionsHelpers.NewDefaultTesting(gt)
 	tp := helpers.NewTestParams(func(tp *e2eutils.TestParams) {})
 	env := helpers.NewL2FaultProofEnv(t, testCfg, tp, helpers.NewBatcherCfg())
@@ -182,7 +182,7 @@ func Test_ProgramAction_WithdrawalsRootBeforeAtAndAfterIsthmus(gt *testing.T) {
 
 	isthmusOffset := 2
 
-	testWithdrawlsRootIsthmus := func(gt *testing.T, testCfg *helpers.TestCfg[testCase]) {
+	testWithdrawalsRootIsthmus := func(gt *testing.T, testCfg *helpers.TestCfg[testCase]) {
 		t := actionsHelpers.NewDefaultTesting(gt)
 		tp := helpers.NewTestParams(func(tp *e2eutils.TestParams) {})
 		var setIsthmusTime = func(dc *genesis.DeployConfig) {
@@ -260,7 +260,7 @@ func Test_ProgramAction_WithdrawalsRootBeforeAtAndAfterIsthmus(gt *testing.T) {
 			test.name,
 			test,
 			helpers.NewForkMatrix(helpers.Holocene),
-			testWithdrawlsRootIsthmus,
+			testWithdrawalsRootIsthmus,
 		)
 	}
 	matrix.Run(gt)

op-service/txmgr/txmgr.go

@@ -158,7 +158,7 @@ func NewSimpleTxManager(name string, l log.Logger, m metrics.TxMetricer, cfg CLI
 	return NewSimpleTxManagerFromConfig(name, l, m, conf)
 }
 
-// NewSimpleTxManager initializes a new SimpleTxManager with the passed Config.
+// NewSimpleTxManagerFromConfig initializes a new SimpleTxManager with the passed Config.
 func NewSimpleTxManagerFromConfig(name string, l log.Logger, m metrics.TxMetricer, conf *Config) (*SimpleTxManager, error) {
 	if err := conf.Check(); err != nil {
 		return nil, fmt.Errorf("invalid config: %w", err)

packages/contracts-bedrock/book/src/policies/versioning.md

@@ -77,7 +77,7 @@ Versioning for monorepo releases works as follows:
 
 ## Optimism Contracts Manager (OPCM) Versioning
 
-The [OPCM](https://github.com/ethereum-optimism/optimism/blob/main/packages/contracts-bedrock/src/L1/OPContractsManager.sol) is the contract that manages the deployment of all contracts on L1.
+The [OPCM](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/L1/OPContractsManager.sol) is the contract that manages the deployment of all contracts on L1.
 
 The `OPCM` is the source of truth for the contracts that belong in a release, available as on-chain addresses by querying [the `getImplementations` function](https://github.com/ethereum-optimism/optimism/blob/4c8764f0453e141555846d8c9dd2af9edbc1d014/packages/contracts-bedrock/src/L1/OPContractsManager.sol#L1061).
 
@@ -148,4 +148,3 @@ Now there are two scenarios for the PR that merges the release branch back into
     - In practice, this one unlikely to occur when using inheritance for feature development, as specified in [Smart Contract Feature Development](https://github.com/ethereum-optimism/design-docs/blob/main/smart-contract-feature-development.md) architecture. It's more likely that (1) is the case, and we merge the version change into the base contract.
 
 This flow also provides a dedicated branch for each release, making it easy to deploy a patch or bug fix, regardless of other changes that may have occurred on develop since the release.
-