applying suggestions

AztecProtocol · May 20, 2024 · 1b4dd27 · 1b4dd27
1 parent 2188884
commit 1b4dd27
Show file tree

Hide file tree

Showing 19 changed files with 3 additions and 1,197 deletions.
diff --git a/docs/docs/aztec/concepts/smart_contracts/communication/cross_chain_calls.md b/docs/docs/aztec/concepts/smart_contracts/communication/cross_chain_calls.md
diff --git a/docs/docs/aztec/core_components.md b/docs/docs/aztec/core_components.md
@@ -39,7 +39,7 @@ A user of the Aztec network will interact with the network through Aztec.js. Azt
 
 ### Private Execution Environment
 
-The PXE provides a secure environment for the execution of sensitive operations, ensuring private information and decrypted data are not accessible to unauthorized applications. It hides the details of the [state model](/aztec/concepts/state_model/index.md) from end users, but the state model is important for Aztec developers to understand as it has implications for [private/public execution](/aztec/concepts/smart_contracts/communication/public_private_calls.md) and [L1/L2 communication](/aztec/concepts/smart_contracts/communication/cross_chain_calls). The PXE also includes the [ACIR Simulator](/aztec/concepts/pxe/acir_simulator.md) for private executions and the KeyStore for secure key management.
+The PXE provides a secure environment for the execution of sensitive operations, ensuring private information and decrypted data are not accessible to unauthorized applications. It hides the details of the [state model](/aztec/concepts/state_model/index.md) from end users, but the state model is important for Aztec developers to understand as it has implications for [private/public execution](/aztec/concepts/smart_contracts/communication/public_private_calls.md) and [L1/L2 communication](/protocol-specs/l1-smart-contracts/index.md). The PXE also includes the [ACIR Simulator](/aztec/concepts/pxe/acir_simulator.md) for private executions and the KeyStore for secure key management.
 
 Procedurally, the PXE sends results of private function execution and requests for public function executions to the [sequencer](/aztec/concepts/nodes_clients/sequencer), which will update the state of the rollup.
 

diff --git a/...ocs/guides/smart_contracts/writing_contracts/portals/communicate_with_portal.md b/...ocs/guides/smart_contracts/writing_contracts/portals/communicate_with_portal.md
@@ -2,7 +2,7 @@
 title: Communicating with L1
 ---
 
-Is this your first time hearing the word `Portal`? Check out the [concepts section](/aztec/concepts/smart_contracts/communication/cross_chain_calls).
+Is this your first time hearing the word `Portal`? Check out the [concepts section](../../../../protocol-specs/l1-smart-contracts/index.md).
 
 Follow the [token bridge tutorial](/tutorials/contract_tutorials/advanced/token_bridge) for hands-on experience writing and deploying a Portal contract.
 

diff --git a/docs/docs/guides/smart_contracts/writing_contracts/portals/deploy_with_portal.md b/docs/docs/guides/smart_contracts/writing_contracts/portals/deploy_with_portal.md
diff --git a/docs/docs/guides/smart_contracts/writing_contracts/portals/index.md b/docs/docs/guides/smart_contracts/writing_contracts/portals/index.md
@@ -2,6 +2,4 @@
 title: Portals
 ---
 
-A portal is a point of contact between L1 and a contract on Aztec. For applications such as token bridges, this is the point where the tokens are held on L1 while used in L2.
-
-As outlined in [Communication](/aztec/concepts/smart_contracts/communication/cross_chain_calls), an Aztec L2 contract is linked to _ONE_ L1 address at time of deployment (specified by the developer). This L1 address is the only address that can send messages to that specific L2 contract, and the only address that can receive messages sent from the L2 contract to L1. Note, that a portal doesn't actually need to be a contract, it could be any address on L1.
+A portal is a point of contact between L1 and a contract on Aztec. For applications such as token bridges, this is the point where the tokens are held on L1 while used in L2. Note, that a portal doesn't actually need to be a contract, it could be any address on L1.
diff --git a/docs/docs/reference/aztecjs/accounts/_category_.yml b/docs/docs/reference/aztecjs/accounts/_category_.yml
diff --git a/docs/docs/reference/aztecjs/accounts/classes/_category_.yml b/docs/docs/reference/aztecjs/accounts/classes/_category_.yml
diff --git a/docs/docs/reference/aztecjs/accounts/classes/defaults.DefaultAccountContract.md b/docs/docs/reference/aztecjs/accounts/classes/defaults.DefaultAccountContract.md
diff --git a/docs/docs/reference/aztecjs/accounts/classes/defaults.DefaultAccountInterface.md b/docs/docs/reference/aztecjs/accounts/classes/defaults.DefaultAccountInterface.md