Smart contracts cleanup #1642

Author: LandauRaz

.htaccess

@@ -411,3 +411,10 @@ RewriteRule ^architecture-and-concepts/network-architecture/fee-mechanism$ /arch
 RewriteRule ^architecture-and-concepts/network-architecture/messaging-mechanism$ /architecture-and-concepts/messaging? [R=301,L]
 RewriteRule ^architecture-and-concepts/network-architecture/starknet-state$ /architecture-and-concepts/state? [R=301,L]
 RewriteRule ^architecture-and-concepts/network-architecture/messaging-reference$ /resources/messaging-reference? [R=301,L]
+RewriteRule ^architecture-and-concepts/smart-contracts/starknet-events/$ https://book.cairo-lang.org/ch101-03-contract-events.html [R=301,L]
+RewriteRule ^architecture-and-concepts/smart-contracts/execution-info/$ / [R=301,L]
+RewriteRule ^architecture-and-concepts/smart-contracts/compiled-class-hash/$ / [R=301,L]
+RewriteRule ^architecture-and-concepts/smart-contracts/contract-address/$ https://book.cairo-lang.org/ch100-01-contracts-classes-and-instances.html [R=301,L]
+RewriteRule ^architecture-and-concepts/smart-contracts/class-hash/$ https://book.cairo-lang.org/ch100-01-contracts-classes-and-instances.html [R=301,L]
+RewriteRule ^architecture-and-concepts/smart-contracts/contract-classes/$ https://book.cairo-lang.org/ch100-01-contracts-classes-and-instances.html [R=301,L]
+RewriteRule ^architecture-and-concepts/smart-contracts/cairo-and-sierra/$ https://book.cairo-lang.org/appendix-09-sierra.html [R=301,L]

components/Starknet/modules/architecture-and-concepts/nav.adoc

@@ -12,7 +12,6 @@
     ** xref:economics-of-starknet.adoc[Tokenomics]
 * Stack
     ** https://book.cairo-lang.org/[Cairo ↗^]
-    ** xref:smart-contracts/cairo-and-sierra.adoc[]
     ** xref:sharp.adoc[SHARP]
     ** xref:os.adoc[SNOS]
     ** xref:starkgate.adoc[]

components/Starknet/modules/architecture-and-concepts/pages/blocks.adoc

@@ -135,7 +135,7 @@ Note that the signature is itself a (possibly empty) array of field elements.
 [discrete]
 === Event hash
 
-The hash of an xref:../smart-contracts/starknet-events.adoc[event] emitted by a contract whose address is `emitter_address` and a transaction whose hash is `tx_hash` is defined by:
+The hash of an https://book.cairo-lang.org/ch101-03-contract-events.html[event^] emitted by a contract whose address is `emitter_address` and a transaction whose hash is `tx_hash` is defined by:
 
 [,,subs="quotes"]
 ----

components/Starknet/modules/architecture-and-concepts/pages/messaging.adoc

@@ -248,6 +248,6 @@ Since L1 handler transactions are not initiated by an account, invoking link:htt
 
 == Additional resources
 
-* xref:architecture-and-concepts:smart-contracts/system-calls-cairo1.adoc#send_message_to_L1[`send_message_to_L1`] syscall
+* https://book.cairo-lang.org/appendix-08-system-calls.html#send_message_to_l1[`send_message_to_L1`^] syscall
 * link:https://github.com/starkware-libs/cairo-lang/blob/54d7e92a703b3b5a1e07e9389608178129946efc/src/starkware/starknet/solidity/IStarknetMessaging.sol#L13[`sendMessageToL2`] function on the Starknet Core Contract
 * For more information on how messaging works within the Starknet Core Contract, including details on coding, see link:https://book.cairo-lang.org/ch16-04-L1-L2-messaging.html[L1-L2 Messaging] in _The Cairo Book: The Cairo Programming Language_

components/Starknet/modules/architecture-and-concepts/pages/os.adoc

@@ -43,12 +43,12 @@ Contract calls are in fact done non-deterministically, i.e. the contract's respo
 [id="syscall-mechanism"]
 === Syscall mechanism
 
-A contract can invoke xref:smart-contracts/system-calls-cairo1.adoc[system calls] throughout its execution, which pass the control from the currently executing contract to SNOS itself. Such operations are required when a contract needs information that does not exist within its code, e.g. accessing the Starknet state to read a storage value or to call another contract.
+A contract can invoke https://book.cairo-lang.org/appendix-08-system-calls.html[system calls^] throughout its execution, which pass the control from the currently executing contract to SNOS itself. Such operations are required when a contract needs information that does not exist within its code, e.g. accessing the Starknet state to read a storage value or to call another contract.
 
 SNOS's code heavily relies on non-determinism to handle system calls. Whenever a contract invokes some syscall, the request, alongside the guessed response, is recorded in a syscalls array.
 At the end of every entry point execution, we go over the syscalls array and verify that the responses were correct (for more details, see the https://github.com/starkware-libs/cairo-lang/blob/8e11b8cc65ae1d0959328b1b4a40b92df8b58595/src/starkware/starknet/core/os/execution/execute_entry_point.cairo#L286[`execute_entry_point` function in `execute_transactions.cairo`^]).
 
-For syscalls such as xref:architecture-and-concepts:smart-contracts/system-calls-cairo1.adoc#get_execution_info[`get_execution_info`], 
+For syscalls such as https://book.cairo-lang.org/appendix-08-system-calls.html#get_execution_info[`get_execution_info`^], 
 which returns the block hash and number, correctness means consistency with the value given to SNOS as input. For contract calls, however, one needs to execute the called contract and verify that the actual response and the guessed response are identical. But how can we guess the responses to all the contract calls before executing them? For that, it is important to distinguish two different styles-of-execution that a Starknet block goes through:
 
 * The first one is done by a sequencer, when constructing the block from incoming transactions