contracts: fixes around recommended v1.6.0

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

@@ -83,9 +83,13 @@ single contract.
 Production users should deploy their L1 contracts from a contracts release.
 All contracts releases are on git tags with the following format:
 `op-contracts/vX.Y.Z`. If you're deploying a new standard chain, you should
-deploy the [Fault Proof Fixes release](https://github.com/ethereum-optimism/optimism/releases/tag/op-contracts%2Fv1.6.0).
-We're working on writing more documentation to prepare OP Stack chain operators
-to run a fault proof chain effectively.
+deploy the [Fault Proof Fixes release](https://github.com/ethereum-optimism/optimism/releases/tag/op-contracts%2Fv1.6.0) with the permissioned game type
+enabled.
+Starting with permissioned fault proofs gives chain operators time to get comfortable
+running the additional infrastructure requirements: [op-challenger](https://github.com/ethereum-optimism/optimism/tree/develop/op-challenger) and
+[monitoring](https://github.com/ethereum-optimism/monitorism/tree/main). There are also
+additional changes to the economics of operating a permissionless fault proof that chain
+operators should have a firm understanding of. 
 
 ## Next Steps
 

pages/stack/smart-contracts.mdx

@@ -37,7 +37,7 @@ Contract releases have a component name of `op-contracts` and therefore are tagg
 
 <Callout type="info">
   Note: While these are a governance approved contract release, the recommended 
-  release for new production chains is `op-contracts/v1.3.0`. 
+  release for new production chains is `op-contracts/v1.6.0`. 
 </Callout>
 
 The Safe Extensions protocol upgrade is intended to increase the security and