chore(docs): re-structuring smart contracts how-to-guides

Author: signorecello

docs/docs/aztec/concepts/accounts/index.md

@@ -73,7 +73,7 @@ A request for executing an action requires:
 - The initial function to call (usually `entrypoint`).
 - The arguments (which encode the private and public calls to run as well as any signatures).
 
-Read more about how to write an account contract [here](../../../developers/tutorials/contract_tutorials/write_accounts_contract.md).
+Read more about how to write an account contract in the [account development guide](../../../developers/guides/js_apps/create_account.md).
 
 ### Non-standard entrypoints
 

docs/docs/aztec/concepts/accounts/keys.md

@@ -106,7 +106,7 @@ When it comes to storing the signing key in a private note, there are several de
 
 #### Using Delayed Public Mutable state
 
-By [Delayed Public Mutable](../../../developers/guides/smart_contracts/storage_types.md#delayed-public-mutable) we mean privately readable publicly mutable state.
+By [Delayed Public Mutable](../../../developers/guides/smart_contracts/how_to_define_storage.md#delayed-public-mutable) we mean privately readable publicly mutable state.
 
 To make public state accessible privately, there is a delay window in public state updates. One needs this window to be able to generate proofs client-side. This approach would not generate additional nullifiers and commitments for each transaction while allowing the user to rotate their key. However, this causes every transaction to now have a time-to-live determined by the frequency of the delayed mutable state, as well as imposing restrictions on how fast keys can be rotated due to minimum delays.
 

docs/docs/aztec/concepts/advanced/authwit.md

@@ -141,4 +141,4 @@ We don't need to limit ourselves to the `transfer` function, we can use the same
 
 ### Next Steps
 
-Check out the [developer documentation](../../../developers/guides/smart_contracts/authwit.md) to see how to implement this in your own contracts.
+Check out the [developer documentation](../../../developers/guides/smart_contracts/how_to_use_authwit.md) to see how to implement this in your own contracts.

docs/docs/aztec/concepts/call_types.md

@@ -149,7 +149,7 @@ aztec = { git = "https://github.com/AztecProtocol/aztec-packages/", tag = "#incl
 
 Even with the router contract achieving good privacy is hard.
 For example, if the value being checked against is unique and stored in the contract's public storage, it's then simple to find private transactions that are using that value in the enqueued public reads, and therefore link them to this contract.
-For this reason it is encouraged to try to avoid public function calls and instead privately read [Shared State](../../developers/guides/smart_contracts/storage_types.md#delayed-public-mutable) when possible.
+For this reason it is encouraged to try to avoid public function calls and instead privately read [Shared State](../../developers/guides/smart_contracts/how_to_define_storage.md#delayed-public-mutable) when possible.
 
 ### Public Execution
 

docs/docs/aztec/concepts/wallets/index.md

@@ -7,7 +7,7 @@ description: Overview of wallet responsibilities in Aztec including account mana
 
 On this page we will cover the main responsibilities of a wallet in the Aztec network.
 
-Refer to [writing an account contract](../../../developers/tutorials/contract_tutorials/write_accounts_contract.md) for a tutorial on how to write a contract to back a user's account.
+Refer to [creating accounts](../../../developers/guides/js_apps/create_account.md) for guidance on account creation and management.
 
 Go to [wallet architecture](./architecture.md) for an overview of its architecture and a reference on the interface a wallet must implement.
 

docs/docs/aztec/smart_contracts/contract_creation.md

@@ -61,7 +61,7 @@ Aztec makes an important distinction between initialization and public deploymen
 
 ### Initialization
 
-Contract constructors are not enshrined in the protocol, but handled at the application circuit level. Constructors are methods used for initializing a contract, either private or public, and contract classes may declare more than a single constructor. They can be declared by the `#[initializer]` macro. You can read more about how to use them on the [Defining Initializer Functions](../../developers/guides/smart_contracts/define_functions.md#initializer-functions) page.
+Contract constructors are not enshrined in the protocol, but handled at the application circuit level. Constructors are methods used for initializing a contract, either private or public, and contract classes may declare more than a single constructor. They can be declared by the `#[initializer]` macro. You can read more about how to use them on the [Defining Initializer Functions](../../developers/guides/smart_contracts/how_to_define_functions.md#initializer-functions) page.
 
 A contract must ensure:
 

docs/docs/aztec/smart_contracts/functions/index.md

@@ -24,7 +24,7 @@ There are also special oracle functions, which can get data from outside of the
 ## Learn more about functions
 
 - [How function visibility works in Aztec](./visibility.md)
-- How to write an [initializer function](../../../developers/guides/smart_contracts/define_functions.md#initializer-functions)
+- How to write an [initializer function](../../../developers/guides/smart_contracts/how_to_define_functions.md#initializer-functions)
 - [Oracles](../oracles/index.md) and how Aztec smart contracts might use them
 - [How functions work under the hood](./attributes.md)