addressing review

Author: sbvegan

pages/builders/chain-operators/deploy/smart-contracts.mdx

@@ -10,7 +10,7 @@ import { Callout } from 'nextra/components'
 
 The following guide shows you how to deploy the OP Stack L1 smart contracts.
 The primary development branch is `develop`, however you should only deploy
-official contract releases. You can visit the see the [smart contract overview](/stack/protocol/rollup/smart-contracts)
+official contract releases. You can visit the see the [smart contract overview](/stack/smart-contracts)
 for the official release versions. **Changes to the smart contracts are
 generally not considered backwards compatible.**
 
@@ -74,7 +74,6 @@ DEPLOY_CONFIG_PATH=<PATH_TO_MY_DEPLOY_CONFIG> \
 
 ### Deploying a single contract
 
-All functions for deploying a single contract are public, meaning that
 All functions for deploying a single contract are public, meaning that
 the `--sig` argument to forge script can be used to target the deployment of a
 single contract.

pages/builders/chain-operators/management/best-practices.mdx

@@ -41,6 +41,8 @@ After deploying your contracts on Ethereum, you should keep a record of all the
 deployment artifacts:
 
 *   Contract release tag and commit hash
+*   Contract deployment configuration file. This is the JSON file you created
+and passed to the deployment script when you deployed the contracts.
 *   Contract deployment directory with smart contract artifacts. This is
 created in [packages/contracts-bedrock/deployments](https://github.com/ethereum-optimism/optimism/tree/develop/packages/contracts-bedrock/deployments)
 *   The rollup configuration file that you generated after the contract