applying suggestions

AztecProtocol · May 20, 2024 · 23d6590 · 23d6590
1 parent edf2fe9
commit 23d6590
Show file tree

Hide file tree

Showing 5 changed files with 3 additions and 205 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.