From ef7b40751a79e852c4e2c39d573fdfb7574cf4b6 Mon Sep 17 00:00:00 2001 From: LHerskind Date: Tue, 19 Sep 2023 22:06:52 +0000 Subject: [PATCH] chore: fix broken links --- docs/docs/dev_docs/contracts/syntax/main.md | 2 +- docs/docs/dev_docs/contracts/syntax/storage.md | 2 +- docs/docs/dev_docs/dapps/tutorials/contract_interaction.md | 2 +- docs/docs/dev_docs/testing/testing.md | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/docs/dev_docs/contracts/syntax/main.md b/docs/docs/dev_docs/contracts/syntax/main.md index c47a2879cc91..7dfa37376c76 100644 --- a/docs/docs/dev_docs/contracts/syntax/main.md +++ b/docs/docs/dev_docs/contracts/syntax/main.md @@ -10,7 +10,7 @@ Aztec.nr contains abstractions which remove the need to understand the low-level - Public and private [state variable types](./state_variables.md) - Some pre-designed notes -- Functions for [emitting](../events.md) encrypted and unencrypted logs +- Functions for [emitting](./events.md) encrypted and unencrypted logs - [Oracle functions](./functions.md#oracle-functions) for accessing: - private state - secrets diff --git a/docs/docs/dev_docs/contracts/syntax/storage.md b/docs/docs/dev_docs/contracts/syntax/storage.md index 2e7019daeba3..3d5c06c91695 100644 --- a/docs/docs/dev_docs/contracts/syntax/storage.md +++ b/docs/docs/dev_docs/contracts/syntax/storage.md @@ -8,7 +8,7 @@ An example of such a struct could be as follow: #include_code storage-struct-declaration /yarn-project/noir-contracts/src/contracts/docs_example_contract/src/main.nr rust :::info -If your storage include private state variables it must include a `compute_note_hash_and_nullifier` function to allow the RPC to process encrypted events, see [encrypted events](./../events.md#processing-encrypted-events) for more. +If your storage include private state variables it must include a `compute_note_hash_and_nullifier` function to allow the RPC to process encrypted events, see [encrypted events](./events.md#processing-encrypted-events) for more. ::: In here, we are setting up a mix of public and private state variables. The public state variables can be read by anyone, and functions manipulating them are executed by the sequence, we will see more to this in [functions](./functions.md#public-functions) in a few moments. The private state variables are only readable by their owner, or people whom the owner have shared the data with. diff --git a/docs/docs/dev_docs/dapps/tutorials/contract_interaction.md b/docs/docs/dev_docs/dapps/tutorials/contract_interaction.md index 3f4508a2f2fa..186ddb55b126 100644 --- a/docs/docs/dev_docs/dapps/tutorials/contract_interaction.md +++ b/docs/docs/dev_docs/dapps/tutorials/contract_interaction.md @@ -116,7 +116,7 @@ Balance of 0x226f8087792beff8d5009eb94e65d2a4a505b70baf4a9f28d33c8d620b0ba972: 0 Balance of 0x0e1f60e8566e2c6d32378bdcadb7c63696e853281be798c107266b8c3a88ea9b: 0 ``` -Public functions can emit [unencrypted public logs](../../contracts/events.md#unencrypted-events), which we can query via the RPC Server interface. In particular, the public token contract emits a generic `Coins minted` whenever the `mint` method is called: +Public functions can emit [unencrypted public logs](../../contracts/syntax/events.md#unencrypted-events), which we can query via the RPC Server interface. In particular, the public token contract emits a generic `Coins minted` whenever the `mint` method is called: #include_code unencrypted_log yarn-project/noir-contracts/src/contracts/public_token_contract/src/main.nr rust diff --git a/docs/docs/dev_docs/testing/testing.md b/docs/docs/dev_docs/testing/testing.md index ef2ce16123ac..d8bdf31adbe7 100644 --- a/docs/docs/dev_docs/testing/testing.md +++ b/docs/docs/dev_docs/testing/testing.md @@ -149,7 +149,7 @@ We can query the RPC server for all notes encrypted for a given user in a contra ### Logs -Last but not least, we can check the logs of [events](../contracts/events.md) emitted by our contracts. Contracts in Aztec can emit both [encrypted](../contracts/events.md#encrypted-events) and [unencrypted](../contracts/events.md#unencrypted-events) events. +Last but not least, we can check the logs of [events](../contracts/syntax/events.md) emitted by our contracts. Contracts in Aztec can emit both [encrypted](../contracts/syntax/events.md#encrypted-events) and [unencrypted](../contracts/syntax/events.md#unencrypted-events) events. :::info At the time of this writing, only unencrypted events can be queried directly. Encrypted events are always assumed to be encrypted notes.