From d86edd026df71180ddb7d1424ee8d6b7089da72b Mon Sep 17 00:00:00 2001
From: Michael Mueller <mich@elmueller.net>
Date: Wed, 15 Feb 2023 17:19:27 +0100
Subject: [PATCH 1/2] Update docs and links for ink! 4.0

---
 docs/basics/debugging.md                      |  4 +--
 docs/basics/env-functions.md                  | 18 +++++------
 docs/basics/metadata.md                       |  2 +-
 docs/basics/testing.md                        |  2 +-
 docs/basics/trait-definitions.md              |  2 +-
 docs/datastructures/custom.md                 | 10 +++----
 docs/datastructures/mapping.md                |  2 +-
 docs/datastructures/overview.md               |  4 +--
 docs/datastructures/storage-in-metadata.md    |  2 +-
 docs/datastructures/storage-layout.md         |  6 ++--
 docs/faq/faq.md                               |  8 ++---
 docs/faq/migrating-from-ink-3-to-4.md         | 30 +++++++++----------
 docs/intro/intro.mdx                          |  5 ----
 docusaurus.config.js                          |  2 +-
 .../current/basics/debugging.md               |  4 +--
 .../current/basics/env-functions.md           | 18 +++++------
 .../current/basics/testing.md                 |  2 +-
 .../current/basics/trait-definitions.md       |  2 +-
 .../current/datastructures/custom.md          | 10 +++----
 .../current/datastructures/mapping.md         |  2 +-
 .../current/datastructures/overview.md        |  4 +--
 .../datastructures/storage-in-metadata.md     |  2 +-
 .../current/datastructures/storage-layout.md  |  6 ++--
 .../current/faq/faq.md                        |  8 ++---
 .../current/intro/intro.mdx                   |  5 ----
 25 files changed, 75 insertions(+), 85 deletions(-)

diff --git a/docs/basics/debugging.md b/docs/basics/debugging.md
index 8c4fa9912e..c555d38cab 100644
--- a/docs/basics/debugging.md
+++ b/docs/basics/debugging.md
@@ -19,8 +19,8 @@ There are three ways to debug your ink! contract currently:
 ### How do I print to the terminal console from ink!?
 
 You can use those two macros:
-* [`ink::env::debug_println!`](https://docs.rs/ink_env/4.0.0-rc/ink_env/macro.debug_println.html)
-* [`ink::env::debug_print!`](https://docs.rs/ink_env/4.0.0-rc/ink_env/macro.debug_print.html)
+* [`ink::env::debug_println!`](https://docs.rs/ink_env/4.0.0/ink_env/macro.debug_println.html)
+* [`ink::env::debug_print!`](https://docs.rs/ink_env/4.0.0/ink_env/macro.debug_print.html)
 
 There are three things you have to do for the debug messages to show up on the console:
 
diff --git a/docs/basics/env-functions.md b/docs/basics/env-functions.md
index 07c4edb865..bce5e172b1 100644
--- a/docs/basics/env-functions.md
+++ b/docs/basics/env-functions.md
@@ -4,7 +4,7 @@ slug: /basics/environment-functions
 ---
 
 ink! exposes a number of handy environment functions.
-A full overview [is found here](https://docs.rs/ink_env/4.0.0-rc/ink_env/#functions).
+A full overview [is found here](https://docs.rs/ink_env/4.0.0/ink_env/#functions).
 
 In an `#[ink(constructor)]`  use `Self::env()` to access those,
 in an `#[ink(message)]` use `self.env()`.
@@ -12,11 +12,11 @@ So e.g. `Self::env().caller()` or `self.env().caller()`.
 
 Some handy functions include:
 
-* [`caller()`](https://docs.rs/ink_env/4.0.0-rc/ink_env/fn.caller.html): Returns the address of the caller of the executed contract.
-* [`account_id()`](https://docs.rs/ink_env/4.0.0-rc/ink_env/fn.account_id.html): Returns the account ID of the executed contract.
-* [`balance()`](https://docs.rs/ink_env/4.0.0-rc/ink_env/fn.balance.html): Returns the balance of the executed contract.
-* [`block_number()`](https://docs.rs/ink_env/4.0.0-rc/ink_env/fn.block_number.html): Returns the current block number.
-* [`emit_event(…)`](https://docs.rs/ink_env/4.0.0-rc/ink_env/fn.emit_event.html): Emits an event with the given event data.
-* [`transfer(…)`](https://docs.rs/ink_env/4.0.0-rc/ink_env/fn.transfer.html): Transfers value from the contract to the destination account ID.
-* [`hash_bytes(…)`](https://docs.rs/ink_env/4.0.0-rc/ink_env/fn.hash_bytes.html): Conducts the crypto hash of the given input and stores the result in output.
-* […and many more](https://docs.rs/ink_env/4.0.0-rc/ink_env/#functions).
+* [`caller()`](https://docs.rs/ink_env/4.0.0/ink_env/fn.caller.html): Returns the address of the caller of the executed contract.
+* [`account_id()`](https://docs.rs/ink_env/4.0.0/ink_env/fn.account_id.html): Returns the account ID of the executed contract.
+* [`balance()`](https://docs.rs/ink_env/4.0.0/ink_env/fn.balance.html): Returns the balance of the executed contract.
+* [`block_number()`](https://docs.rs/ink_env/4.0.0/ink_env/fn.block_number.html): Returns the current block number.
+* [`emit_event(…)`](https://docs.rs/ink_env/4.0.0/ink_env/fn.emit_event.html): Emits an event with the given event data.
+* [`transfer(…)`](https://docs.rs/ink_env/4.0.0/ink_env/fn.transfer.html): Transfers value from the contract to the destination account ID.
+* [`hash_bytes(…)`](https://docs.rs/ink_env/4.0.0/ink_env/fn.hash_bytes.html): Conducts the crypto hash of the given input and stores the result in output.
+* […and many more](https://docs.rs/ink_env/4.0.0/ink_env/#functions).
diff --git a/docs/basics/metadata.md b/docs/basics/metadata.md
index 6ad25ba033..e1b533a910 100644
--- a/docs/basics/metadata.md
+++ b/docs/basics/metadata.md
@@ -192,7 +192,7 @@ comes from the smart contracting language itself, and not the contract nor the u
 environment (e.g `pallet-contracts`).
 
 All ink! messages and constructors now return a `Result` which uses this as the `Error`
-variant (see the [`LangError`](https://docs.rs/ink/4.0.0-rc/ink/enum.LangError.html) docs for more).
+variant (see the [`LangError`](https://docs.rs/ink/4.0.0/ink/enum.LangError.html) docs for more).
 
 :::
 
diff --git a/docs/basics/testing.md b/docs/basics/testing.md
index a6854735e2..f90ba99a53 100644
--- a/docs/basics/testing.md
+++ b/docs/basics/testing.md
@@ -61,7 +61,7 @@ You then have fine-grained control over how a contract is called;
 for example you can influence the block advancement, the value transferred to it,
 by which account it is called, which storage it is run with, etc..
 
-See the [`examples/erc20`](https://github.com/paritytech/ink/blob/master/examples/erc20/lib.rs) contract on how to utilize those or [the documentation](https://docs.rs/ink/4.0.0-rc/ink/attr.test.html) for details.
+See the [`examples/erc20`](https://github.com/paritytech/ink/blob/master/examples/erc20/lib.rs) contract on how to utilize those or [the documentation](https://docs.rs/ink/4.0.0/ink/attr.test.html) for details.
 
 At the moment there are some known limitations to our off-chain environment,
 and we are working on making it behave as close to the real chain environment
diff --git a/docs/basics/trait-definitions.md b/docs/basics/trait-definitions.md
index beb12bf916..2643d9e4a8 100644
--- a/docs/basics/trait-definitions.md
+++ b/docs/basics/trait-definitions.md
@@ -96,7 +96,7 @@ Marks trait definitions to ink! as special ink! trait definitions.
 
 There are some restrictions that apply to ink! trait definitions that
 this macro checks. Also ink! trait definitions are required to have specialized
-structure so that the main [`#[ink::contract]`](https://docs.rs/ink/4.0.0-rc/ink/attr.contract.html) macro can
+structure so that the main [`#[ink::contract]`](https://docs.rs/ink/4.0.0/ink/attr.contract.html) macro can
 properly generate code for its implementations.
 
 # Example: Definition
diff --git a/docs/datastructures/custom.md b/docs/datastructures/custom.md
index 7ef6f709e2..860aad9287 100644
--- a/docs/datastructures/custom.md
+++ b/docs/datastructures/custom.md
@@ -14,7 +14,7 @@ also create their own custom data structures.
 
 ## Using custom types on storage
 Any custom type wanting to be compatible with ink! storage must implement the
-[`Storable`](https://docs.rs/ink_storage_traits/4.0.0-rc/ink_storage_traits/trait.Storable.html)
+[`Storable`](https://docs.rs/ink_storage_traits/4.0.0/ink_storage_traits/trait.Storable.html)
 trait, so it can be SCALE
 [`encoded`](https://docs.rs/parity-scale-codec/3.2.2/parity_scale_codec/trait.Encode.html)
 and
@@ -42,7 +42,7 @@ pub struct ContractStorage {
 ```
 
 Even better: there is a macro
-[`#[ink::storage_item]`](https://docs.rs/ink_macro/4.0.0-rc/ink_macro/attr.storage_item.html),
+[`#[ink::storage_item]`](https://docs.rs/ink_macro/4.0.0/ink_macro/attr.storage_item.html),
 which derives all necessary traits for you. If there is no need to implement any special
 behavior, the above code example can be simplified further as follows:
 
@@ -65,10 +65,10 @@ the relevant trait documentations for more information.
 :::note
 
 The `#[ink::storage_item]` macro is responsible for storage key calculation of 
-non-[`Packed`](https://docs.rs/ink_storage_traits/4.0.0-rc/ink_storage_traits/trait.Packed.html) 
+non-[`Packed`](https://docs.rs/ink_storage_traits/4.0.0/ink_storage_traits/trait.Packed.html) 
 types. Without it, the key for non-`Packed` fields will be zero. Using this macro is 
 necessary if you don't plan to use a
-[`ManualKey`](https://docs.rs/ink_storage_traits/4.0.0-rc/ink_storage_traits/struct.ManualKey.html) 
+[`ManualKey`](https://docs.rs/ink_storage_traits/4.0.0/ink_storage_traits/struct.ManualKey.html) 
 on a non-`Packed` type.
 
 Types with custom implementations of the ink! storage traits can still use this macro only 
@@ -81,7 +81,7 @@ for key calculation by disabling the derives: `#[ink::storage_item(derive = fals
 It is possible to use generic data types in your storage, as long as any generic type
 satisfies the required storage trait bounds. In fact, we already witnessed this in the
 previous sections about the
-[`Mapping`](https://docs.rs/ink_storage/4.0.0-rc/ink_storage/struct.Mapping.html).
+[`Mapping`](https://docs.rs/ink_storage/4.0.0/ink_storage/struct.Mapping.html).
 
 Let's say you want a mapping where accessing a non-existent key should just return
 it's default value, akin to how mappings work in Solidity. Additionally, you want to know
diff --git a/docs/datastructures/mapping.md b/docs/datastructures/mapping.md
index 616e3865d0..8f74bed453 100644
--- a/docs/datastructures/mapping.md
+++ b/docs/datastructures/mapping.md
@@ -8,7 +8,7 @@ hide_title: true
 
 # Working with Mapping
 
-In this section we demonstrate how to work with ink! [`Mapping`](https://docs.rs/ink_storage/4.0.0-rc/ink_storage/struct.Mapping.html).
+In this section we demonstrate how to work with ink! [`Mapping`](https://docs.rs/ink_storage/4.0.0/ink_storage/struct.Mapping.html).
 
 Here is an example of a mapping from a user to a `Balance`:
 
diff --git a/docs/datastructures/overview.md b/docs/datastructures/overview.md
index 011d2d60c6..b9817bf768 100644
--- a/docs/datastructures/overview.md
+++ b/docs/datastructures/overview.md
@@ -10,8 +10,8 @@ hide_title: true
 
 The `ink_storage` crate acts as the standard storage library for ink! smart contracts.
 At the moment it provides two primitives for interacting with storage,
-[`Mapping`](https://docs.rs/ink_storage/4.0.0-rc/ink_storage/struct.Mapping.html)
-and [`Lazy`](https://docs.rs/ink_storage/4.0.0-rc/ink_storage/struct.Lazy.html).
+[`Mapping`](https://docs.rs/ink_storage/4.0.0/ink_storage/struct.Mapping.html)
+and [`Lazy`](https://docs.rs/ink_storage/4.0.0/ink_storage/struct.Lazy.html).
 
 `Mapping` is a mapping of key-value pairs directly to the contract storage. It is very
 similar to traditional hash tables and comparable to the `mapping` type Solidity offers.
diff --git a/docs/datastructures/storage-in-metadata.md b/docs/datastructures/storage-in-metadata.md
index fbf9e1728c..cc86c0ee1f 100644
--- a/docs/datastructures/storage-in-metadata.md
+++ b/docs/datastructures/storage-in-metadata.md
@@ -72,7 +72,7 @@ The storage will be reflected inside the metadata as like follows:
 
 We observe that the storage layout is represented as a tree, where tangible storage values
 end up inside a `leaf`. Because of
-[`Packed`](https://docs.rs/ink_storage_traits/4.0.0-rc/ink_storage_traits/trait.Packed.html)
+[`Packed`](https://docs.rs/ink_storage_traits/4.0.0/ink_storage_traits/trait.Packed.html)
 encoding, leafs can share the same storage key, and
 in order to reach them you'd need to fetch and decode the whole storage cell under this key.
 
diff --git a/docs/datastructures/storage-layout.md b/docs/datastructures/storage-layout.md
index 0469ea7a77..9c9ff9b9cb 100644
--- a/docs/datastructures/storage-layout.md
+++ b/docs/datastructures/storage-layout.md
@@ -31,7 +31,7 @@ extent, the storage API works similar to a traditional key-value database.
 ## Packed vs Non-Packed layout
 
 Types that can be stored entirely under a single storage cell are considered
-[`Packed`](https://docs.rs/ink_storage_traits/4.0.0-rc/ink_storage_traits/trait.Packed.html).
+[`Packed`](https://docs.rs/ink_storage_traits/4.0.0/ink_storage_traits/trait.Packed.html).
 By default, ink! tries to store all storage struct fields under a single storage cell.
 Consequentially, with a `Packed` storage layout, any message interacting with the contract
 storage will always need to operate on the entire contract storage struct.
@@ -132,10 +132,10 @@ large or sparse arrays on contract storage, consider using a `Mapping` instead.
 ## Manual vs. Automatic Key Generation
 
 By default, keys are calculated automatically for you, thanks to the
-[`AutoKey`](https://docs.rs/ink_storage_traits/4.0.0-rc/ink_storage_traits/struct.AutoKey.html)
+[`AutoKey`](https://docs.rs/ink_storage_traits/4.0.0/ink_storage_traits/struct.AutoKey.html)
 primitive. They'll be generated at compile time and ruled out for conflicts.
 However, for non-`Packed` types like `Lazy` or the `Mapping`, the
-[`ManualKey`](https://docs.rs/ink_storage_traits/4.0.0-rc/ink_storage_traits/struct.ManualKey.html)
+[`ManualKey`](https://docs.rs/ink_storage_traits/4.0.0/ink_storage_traits/struct.ManualKey.html)
 primitive allows manual control over the storage key of a field like so:
 
 ```rust
diff --git a/docs/faq/faq.md b/docs/faq/faq.md
index b402999a97..e313061224 100644
--- a/docs/faq/faq.md
+++ b/docs/faq/faq.md
@@ -91,7 +91,7 @@ See the [Chain Extensions](/macros-attributes/chain-extension) section for more
 
 ### How can I use ink! with a Substrate chain with a custom chain config?
 
-Please see [the `env_types` argument](https://docs.rs/ink_macro/4.0.0-rc/ink_macro/attr.contract.html#header-arguments)
+Please see [the `env_types` argument](https://docs.rs/ink_macro/4.0.0/ink_macro/attr.contract.html#header-arguments)
 for the contract macro. It allows you to specify your environment a la 
 `#[ink::contract(env = MyEnvironment)]`.
 
@@ -168,15 +168,15 @@ Rust's standard library consists of three different layers:
 
 A number of crypto hashes are built into the [pallet-contracts](/how-it-works) and
 therefore very efficient to use. We currently support a handful of those, you 
-can view the complete list [here](https://docs.rs/ink_env/4.0.0-rc/ink_env/hash/trait.CryptoHash.html).
+can view the complete list [here](https://docs.rs/ink_env/4.0.0/ink_env/hash/trait.CryptoHash.html).
 
 If you have the urgent need for another crypto hash you could introduce it through
 [Chain Extensions](/macros-attributes/chain-extension)
 or make a proposal to include it into the default set of the `pallet-contracts`.
 
 Using one of the built-in crypto hashes can be done as explained here:
-* [`self.env().hash_bytes()`](https://docs.rs/ink_env/4.0.0-rc/ink_env/fn.hash_bytes.html)
-* [`self.env().hash_encoded()`](https://docs.rs/ink_env/4.0.0-rc/ink_env/fn.hash_encoded.html)
+* [`self.env().hash_bytes()`](https://docs.rs/ink_env/4.0.0/ink_env/fn.hash_bytes.html)
+* [`self.env().hash_encoded()`](https://docs.rs/ink_env/4.0.0/ink_env/fn.hash_encoded.html)
 
 ### Why is it not possible to use floating point data types in ink!? How do I implement returning a decimal number?
 
diff --git a/docs/faq/migrating-from-ink-3-to-4.md b/docs/faq/migrating-from-ink-3-to-4.md
index 747ff194de..a6c8ab9859 100644
--- a/docs/faq/migrating-from-ink-3-to-4.md
+++ b/docs/faq/migrating-from-ink-3-to-4.md
@@ -91,7 +91,7 @@ we removed support for it in [#1403](https://github.com/paritytech/ink/pull/1403
 
 As part of [#1233](https://github.com/paritytech/ink/pull/1233)
 the `eth_compatibility` crate was removed. The `ecdsa_to_eth_address()`
-function from it can now be found [in the `ink_env` crate](https://docs.rs/ink_env/4.0.0-rc/ink_env/fn.ecdsa_to_eth_address.html).
+function from it can now be found [in the `ink_env` crate](https://docs.rs/ink_env/4.0.0/ink_env/fn.ecdsa_to_eth_address.html).
 
 ```rust
 ink_env::ecdsa_to_eth_address(&pub_key, &mut output);
@@ -105,9 +105,9 @@ The return value is the size of the pre-existing value at the specified key if a
 
 Two new useful functions were added:
 
-- [`Mapping::contains(key)`](https://docs.rs/ink_storage/4.0.0-rc/ink_storage/struct.Mapping.html#method.contains)
+- [`Mapping::contains(key)`](https://docs.rs/ink_storage/4.0.0/ink_storage/struct.Mapping.html#method.contains)
   in [#1224](https://github.com/paritytech/ink/pull/1224).
-- [`Mapping::take()`](https://docs.rs/ink_storage/4.0.0-rc/ink_storage/struct.Mapping.html#method.take)
+- [`Mapping::take()`](https://docs.rs/ink_storage/4.0.0/ink_storage/struct.Mapping.html#method.take)
   to get a value while removing it from storage in [#1461](https://github.com/paritytech/ink/pull/1461).
 
 In case you were working around those two functions you can now
@@ -117,10 +117,10 @@ a `get(key).is_none()` instead of `contains(key)`.
 ## Storage functions in `ink_env`
 
 As part of [#1224](https://github.com/paritytech/ink/pull/1224) the return type
-of [`ink_env::set_contract_storage()`](https://docs.rs/ink_env/4.0.0-rc/ink_env/fn.set_contract_storage.html)
+of [`ink_env::set_contract_storage()`](https://docs.rs/ink_env/4.0.0/ink_env/fn.set_contract_storage.html)
 was changed to return an `Option<u32>` instead of `()`.
 
-A new function [`ink_env::take_contract_storage`](https://docs.rs/ink_env/4.0.0-rc/ink_env/fn.take_contract_storage.html)
+A new function [`ink_env::take_contract_storage`](https://docs.rs/ink_env/4.0.0/ink_env/fn.take_contract_storage.html)
 was introduced.
 
 ## Removal of `ink_env::random` function
@@ -177,7 +177,7 @@ for constructors `Result<Constructor::Output, LangError>`).
 This happens even if the message/constructor doesn't have a return type,
 we default to the unit type `()` in that case.
 
-A [`LangError`](https://docs.rs/ink/4.0.0-rc/ink/enum.LangError.html)
+A [`LangError`](https://docs.rs/ink/4.0.0/ink/enum.LangError.html)
 is a type of error which doesn't originate from the contract itself,
 nor from the underlying execution environment (so the Contracts pallet
 in this case).
@@ -319,14 +319,14 @@ better.
 
 ## Updates to the `CallBuilder` and `CreateBuilder` APIs
 There's been several changes to the
-[`CallBuilder`](https://docs.rs/ink_env/4.0.0-rc/ink_env/call/struct.CallBuilder.html) 
+[`CallBuilder`](https://docs.rs/ink_env/4.0.0/ink_env/call/struct.CallBuilder.html) 
 and 
-[`CreateBuilder`](https://docs.rs/ink_env/4.0.0-rc/ink_env/call/struct.CreateBuilder.html)
+[`CreateBuilder`](https://docs.rs/ink_env/4.0.0/ink_env/call/struct.CreateBuilder.html)
 APIs.
 
 In [#1604](https://github.com/paritytech/ink/pull/1604) we renamed the
 `CallBuilder::fire()` method to
-[`CallBuilder::invoke()`](https://docs.rs/ink_env/4.0.0-rc/ink_env/call/struct.CallBuilder.html#method.invoke-2).
+[`CallBuilder::invoke()`](https://docs.rs/ink_env/4.0.0/ink_env/call/struct.CallBuilder.html#method.invoke-2).
 This brings more consistency across our APIs which were already using the `invoke`
 terminology.
 
@@ -335,9 +335,9 @@ we added support for handing
 `LangError`s from the `CreateBuilder` and `CallBuilder`, respectively.
 
 If you want to handle errors from either `Builder` you can use the new
-[`CreateBuilder::try_instantiate()`](https://docs.rs/ink_env/4.0.0-rc/ink_env/call/struct.CreateBuilder.html#method.try_instantiate)
+[`CreateBuilder::try_instantiate()`](https://docs.rs/ink_env/4.0.0/ink_env/call/struct.CreateBuilder.html#method.try_instantiate)
 or 
-[`CallBuilder::try_invoke()`](https://docs.rs/ink_env/4.0.0-rc/ink_env/call/struct.CallBuilder.html#method.try_invoke-1)
+[`CallBuilder::try_invoke()`](https://docs.rs/ink_env/4.0.0/ink_env/call/struct.CallBuilder.html#method.try_invoke-1)
 methods.
 
 Because of the addition of those methods we also removed any error handling from the
@@ -347,10 +347,10 @@ directly, and panic when they encounter an error.
 
 Lastly, in [#1636](https://github.com/paritytech/ink/pull/1636) we added two methods to
 the `CallBuilder` to streamline
-[`Call`](https://docs.rs/ink_env/4.0.0-rc/ink_env/call/struct.Call.html)
+[`Call`](https://docs.rs/ink_env/4.0.0/ink_env/call/struct.Call.html)
 and
-[`DelegateCall`](https://docs.rs/ink_env/4.0.0-rc/ink_env/call/struct.DelegateCall.html)
+[`DelegateCall`](https://docs.rs/ink_env/4.0.0/ink_env/call/struct.DelegateCall.html)
 workflows:
 - For `Call` you can use
-  [`CallBuilder::call()`](https://docs.rs/ink_env/4.0.0-rc/ink_env/call/struct.CallBuilder.html#method.call) (this replaces `CallBuilder::callee()`)
-- For `DelegateCall` you can use [`CallBuilder::delegate()`](https://docs.rs/ink_env/4.0.0-rc/ink_env/call/struct.CallBuilder.html#method.delegate)
+  [`CallBuilder::call()`](https://docs.rs/ink_env/4.0.0/ink_env/call/struct.CallBuilder.html#method.call) (this replaces `CallBuilder::callee()`)
+- For `DelegateCall` you can use [`CallBuilder::delegate()`](https://docs.rs/ink_env/4.0.0/ink_env/call/struct.CallBuilder.html#method.delegate)
diff --git a/docs/intro/intro.mdx b/docs/intro/intro.mdx
index efccf07eaa..313a42d61b 100644
--- a/docs/intro/intro.mdx
+++ b/docs/intro/intro.mdx
@@ -21,11 +21,6 @@ hide_table_of_contents: false
     <a href="https://twitter.com/ink_lang">
         <img style={{height: 25}} src="https://img.shields.io/twitter/follow/ink_lang?label=Follow" />
     </a>
-    <br/>
-    <em>
-    ink! 4.0 was published as a release candidate on Jan 31 '23.<br/>
-    We'll soon publish the full release.
-    </em>
 </center>
 
 <h3 style={{lineHeight: 1.4 + "em", marginTop: 0.5 + "em"}}>
diff --git a/docusaurus.config.js b/docusaurus.config.js
index 747f436c77..e858e85ea0 100644
--- a/docusaurus.config.js
+++ b/docusaurus.config.js
@@ -71,7 +71,7 @@ module.exports = {
         lastVersion: 'current',
         versions: {
           current: {
-            label: '4.0-rc',
+            label: '4.0',
             path: '',
             banner: 'none',
           },
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/basics/debugging.md b/i18n/es/docusaurus-plugin-content-docs/current/basics/debugging.md
index 57c46da32b..246fb7677e 100644
--- a/i18n/es/docusaurus-plugin-content-docs/current/basics/debugging.md
+++ b/i18n/es/docusaurus-plugin-content-docs/current/basics/debugging.md
@@ -17,8 +17,8 @@ Actualmente existen tres maneras de debuggear tu contrato ink!:
 ### ¿Cómo imprimo algo en la consola desde el runtime?
 
 Puedes elegir entre estos dos macros:
-* [`ink::env::debug_println!`](https://docs.rs/ink_env/4.0.0-rc/ink_env/macro.debug_println.html)
-* [`ink::env::debug_print!`](https://docs.rs/ink_env/4.0.0-rc/ink_env/macro.debug_print.html)
+* [`ink::env::debug_println!`](https://docs.rs/ink_env/4.0.0/ink_env/macro.debug_println.html)
+* [`ink::env::debug_print!`](https://docs.rs/ink_env/4.0.0/ink_env/macro.debug_print.html)
 
 Tienes que hacer tres cosas para poder mostrar en la consola los mensajes de debug:
 
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/basics/env-functions.md b/i18n/es/docusaurus-plugin-content-docs/current/basics/env-functions.md
index 83d3ba2c00..bc52170668 100644
--- a/i18n/es/docusaurus-plugin-content-docs/current/basics/env-functions.md
+++ b/i18n/es/docusaurus-plugin-content-docs/current/basics/env-functions.md
@@ -4,7 +4,7 @@ slug: /basics/environment-functions
 ---
 
 ink! expone una serie de funciones de entorno.
-Puedes encontrar una descripción completa [aquí](https://docs.rs/ink_env/4.0.0-rc/ink_env/#functions).
+Puedes encontrar una descripción completa [aquí](https://docs.rs/ink_env/4.0.0/ink_env/#functions).
 
 En `#[ink(constructor)]`  utiliza `Self::env()` para acceder a esos,
 en `#[ink(message)]` utiliza `self.env()`.
@@ -12,11 +12,11 @@ Por ejemplo `Self::env().caller()` o `self.env().caller()`.
 
 Algunas funciones útiles incluyen:
 
-* [`caller()`](https://docs.rs/ink_env/4.0.0-rc/ink_env/fn.caller.html): Devuelve la dirección de la persona que llama del contrato ejecutado.
-* [`account_id()`](https://docs.rs/ink_env/4.0.0-rc/ink_env/fn.account_id.html): Devuelve el account ID del contrato ejecutado.
-* [`balance()`](https://docs.rs/ink_env/4.0.0-rc/ink_env/fn.balance.html): Devuelve el balance del contrato ejecutado.
-* [`block_number()`](https://docs.rs/ink_env/4.0.0-rc/ink_env/fn.block_number.html): Devuelve el número de bloque actual.
-* [`emit_event(…)`](https://docs.rs/ink_env/4.0.0-rc/ink_env/fn.emit_event.html): Emite un evento con los datos del evento dado.
-* [`transfer(…)`](https://docs.rs/ink_env/4.0.0-rc/ink_env/fn.transfer.html): Transfiere valor desde el contrato hasta el account ID del destino.
-* [`hash_bytes(…)`](https://docs.rs/ink_env/4.0.0-rc/ink_env/fn.hash_bytes.html): Realiza el hash criptográfico de la entrada dada y almacena el resultado en la salida.
-* […and many more](https://docs.rs/ink_env/4.0.0-rc/ink_env/#functions).
+* [`caller()`](https://docs.rs/ink_env/4.0.0/ink_env/fn.caller.html): Devuelve la dirección de la persona que llama del contrato ejecutado.
+* [`account_id()`](https://docs.rs/ink_env/4.0.0/ink_env/fn.account_id.html): Devuelve el account ID del contrato ejecutado.
+* [`balance()`](https://docs.rs/ink_env/4.0.0/ink_env/fn.balance.html): Devuelve el balance del contrato ejecutado.
+* [`block_number()`](https://docs.rs/ink_env/4.0.0/ink_env/fn.block_number.html): Devuelve el número de bloque actual.
+* [`emit_event(…)`](https://docs.rs/ink_env/4.0.0/ink_env/fn.emit_event.html): Emite un evento con los datos del evento dado.
+* [`transfer(…)`](https://docs.rs/ink_env/4.0.0/ink_env/fn.transfer.html): Transfiere valor desde el contrato hasta el account ID del destino.
+* [`hash_bytes(…)`](https://docs.rs/ink_env/4.0.0/ink_env/fn.hash_bytes.html): Realiza el hash criptográfico de la entrada dada y almacena el resultado en la salida.
+* […and many more](https://docs.rs/ink_env/4.0.0/ink_env/#functions).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/basics/testing.md b/i18n/es/docusaurus-plugin-content-docs/current/basics/testing.md
index fb2bb07895..cda3a0c46b 100644
--- a/i18n/es/docusaurus-plugin-content-docs/current/basics/testing.md
+++ b/i18n/es/docusaurus-plugin-content-docs/current/basics/testing.md
@@ -62,7 +62,7 @@ por ejemplo puedes influir en el avance del bloque, el valor transferido al mism
 por qué cuenta se llama, con qué almacenamiento se ejecuta, etc.
 
 
-Vea el contrato [`examples/erc20`](https://github.com/paritytech/ink/blob/master/examples/erc20/lib.rs) csobre como utilizarlo o [la documentación](https://docs.rs/ink/4.0.0-rc/ink/attr.test.html) para más detalles.
+Vea el contrato [`examples/erc20`](https://github.com/paritytech/ink/blob/master/examples/erc20/lib.rs) csobre como utilizarlo o [la documentación](https://docs.rs/ink/4.0.0/ink/attr.test.html) para más detalles.
 
 En este momento hay algunas limitaciones conocidas para nuestro entorno off-chain y estamos trabajando
 en hacer que el comportamiento sea lo más cercano posible a un entorno de una red real.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/basics/trait-definitions.md b/i18n/es/docusaurus-plugin-content-docs/current/basics/trait-definitions.md
index b2c5f630a9..522de83a2e 100644
--- a/i18n/es/docusaurus-plugin-content-docs/current/basics/trait-definitions.md
+++ b/i18n/es/docusaurus-plugin-content-docs/current/basics/trait-definitions.md
@@ -95,7 +95,7 @@ Estas limitaciones existen debido a las complejidades técnicas, sin embargo muc
 Marca definiciones trait para ink! como ink! trait definiciones especiales.
 
 Hay algunas restricciones para las definiciones trait de ink! que este macro comprueba. Además las definiciones trait de ink! son necesarias para 
-tener una estructura especializada y que la principial macro [`#[ink::contract]`](https://docs.rs/ink/4.0.0-rc/ink/attr.contract.html) pueda generar correctamente código para su implementación.
+tener una estructura especializada y que la principial macro [`#[ink::contract]`](https://docs.rs/ink/4.0.0/ink/attr.contract.html) pueda generar correctamente código para su implementación.
 
 # Ejemplo: Definición
 
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/datastructures/custom.md b/i18n/es/docusaurus-plugin-content-docs/current/datastructures/custom.md
index 49a5588760..e2a0279e76 100644
--- a/i18n/es/docusaurus-plugin-content-docs/current/datastructures/custom.md
+++ b/i18n/es/docusaurus-plugin-content-docs/current/datastructures/custom.md
@@ -18,7 +18,7 @@ also create their own custom data structures.
 
 ## Using custom types on storage
 Any custom type wanting to be compatible with ink! storage must implement the
-[`Storable`](https://docs.rs/ink_storage_traits/4.0.0-rc/ink_storage_traits/trait.Storable.html)
+[`Storable`](https://docs.rs/ink_storage_traits/4.0.0/ink_storage_traits/trait.Storable.html)
 trait, so it can be SCALE
 [`encoded`](https://docs.rs/parity-scale-codec/3.2.2/parity_scale_codec/trait.Encode.html)
 and
@@ -46,7 +46,7 @@ pub struct ContractStorage {
 ```
 
 Even better: there is a macro
-[`#[ink::storage_item]`](https://docs.rs/ink_macro/4.0.0-rc/ink_macro/attr.storage_item.html),
+[`#[ink::storage_item]`](https://docs.rs/ink_macro/4.0.0/ink_macro/attr.storage_item.html),
 which derives all necessary traits for you. If there is no need to implement any special
 behaviour, the above code example can be simplified further as follows:
 
@@ -69,10 +69,10 @@ the relevant trait documentations for more information.
 :::note
 
 The `#[ink::storage_item]` macro is responsible for storage key calculation of 
-non-[`Packed`](https://docs.rs/ink_storage_traits/4.0.0-rc/ink_storage_traits/trait.Packed.html) 
+non-[`Packed`](https://docs.rs/ink_storage_traits/4.0.0/ink_storage_traits/trait.Packed.html) 
 types. Without it, the key for non-`Packed` fields will be zero. Using this macro is 
 necessary if you don't plan to use a
-[`ManualKey`](https://docs.rs/ink_storage_traits/4.0.0-rc/ink_storage_traits/struct.ManualKey.html) 
+[`ManualKey`](https://docs.rs/ink_storage_traits/4.0.0/ink_storage_traits/struct.ManualKey.html) 
 on a non-`Packed` type.
 
 Types with custom implementations of the ink! storage traits can still use this macro only 
@@ -85,7 +85,7 @@ for key calculation by disabling the derives: `#[ink::storage_item(derive = fals
 It is possible to use generic data types in your storage, as long as any generic type
 satisfies the required storage trait bounds. In fact, we already witnessed this in the
 previous sections about the
-[`Mapping`](https://docs.rs/ink_storage/4.0.0-rc/ink_storage/struct.Mapping.html).
+[`Mapping`](https://docs.rs/ink_storage/4.0.0/ink_storage/struct.Mapping.html).
 
 Let's say you want a mapping where accessing a non-existent key should just return
 it's default value, akin to how mappings work in Solidity. Additionally, you want to know
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/datastructures/mapping.md b/i18n/es/docusaurus-plugin-content-docs/current/datastructures/mapping.md
index 87681a143d..454536696c 100644
--- a/i18n/es/docusaurus-plugin-content-docs/current/datastructures/mapping.md
+++ b/i18n/es/docusaurus-plugin-content-docs/current/datastructures/mapping.md
@@ -12,7 +12,7 @@ hide_title: true
 TODO: Translate to Spanish.
 :::
 
-In this section we demonstrate how to work with ink! [`Mapping`](https://docs.rs/ink_storage/4.0.0-rc/ink_storage/struct.Mapping.html).
+In this section we demonstrate how to work with ink! [`Mapping`](https://docs.rs/ink_storage/4.0.0/ink_storage/struct.Mapping.html).
 
 Here is an example of a mapping from a user to a `Balance`:
 
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/datastructures/overview.md b/i18n/es/docusaurus-plugin-content-docs/current/datastructures/overview.md
index 49aeca2556..19c9bf61a4 100644
--- a/i18n/es/docusaurus-plugin-content-docs/current/datastructures/overview.md
+++ b/i18n/es/docusaurus-plugin-content-docs/current/datastructures/overview.md
@@ -10,8 +10,8 @@ hide_title: true
 
 El crate `ink_storage` actúa como la biblioteca de almacenamiento estándar para los smart contracts ink!.
 En este momento proporciona dos primitivas para interactuar con el storage,
-[`Mapping`](https://docs.rs/ink_storage/4.0.0-rc/ink_storage/struct.Mapping.html)
-y [`Lazy`](https://docs.rs/ink_storage/4.0.0-rc/ink_storage/struct.Lazy.html).
+[`Mapping`](https://docs.rs/ink_storage/4.0.0/ink_storage/struct.Mapping.html)
+y [`Lazy`](https://docs.rs/ink_storage/4.0.0/ink_storage/struct.Lazy.html).
 
 `Mapping` es un mapeo de pares clave-valor directamente en el storage del contrato. 
 Es muy similar a tablas hash tradicionales y comparable con el tipo `mapping` que ofrece Solidity.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/datastructures/storage-in-metadata.md b/i18n/es/docusaurus-plugin-content-docs/current/datastructures/storage-in-metadata.md
index 9e1ecd379a..6a351bb300 100644
--- a/i18n/es/docusaurus-plugin-content-docs/current/datastructures/storage-in-metadata.md
+++ b/i18n/es/docusaurus-plugin-content-docs/current/datastructures/storage-in-metadata.md
@@ -76,7 +76,7 @@ The storage will be reflected inside the metadata as like follows:
 
 We observe that the storage layout is represented as a tree, where tangible storage values
 end up inside a `leaf`. Because of
-[`Packed`](https://docs.rs/ink_storage_traits/4.0.0-rc/ink_storage_traits/trait.Packed.html)
+[`Packed`](https://docs.rs/ink_storage_traits/4.0.0/ink_storage_traits/trait.Packed.html)
 encoding, leafs can share the same storage key, and
 in order to reach them you'd need fetch and decode the whole storage cell under this key.
 
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/datastructures/storage-layout.md b/i18n/es/docusaurus-plugin-content-docs/current/datastructures/storage-layout.md
index 7c19304b97..9cfaa2a586 100644
--- a/i18n/es/docusaurus-plugin-content-docs/current/datastructures/storage-layout.md
+++ b/i18n/es/docusaurus-plugin-content-docs/current/datastructures/storage-layout.md
@@ -35,7 +35,7 @@ extent, the storage API works similar to a traditional key-value database.
 ## Packed vs Non-Packed layout
 
 Types that can be stored entirely under a single storage cell are considered
-[`Packed`](https://docs.rs/ink_storage_traits/4.0.0-rc/ink_storage_traits/trait.Packed.html).
+[`Packed`](https://docs.rs/ink_storage_traits/4.0.0/ink_storage_traits/trait.Packed.html).
 By default, ink! tries to store all storage struct fields under a single storage cell.
 Consequentially, with a `Packed` storage layout, any message interacting with the contract
 storage will always need to operate on the entire contract storage struct.
@@ -136,10 +136,10 @@ large or sparse arrays on contract storage, consider using a `Mapping` instead.
 ## Manual vs. Automatic Key Generation
 
 By default, keys are calculated automatically for you, thanks to the
-[`AutoKey`](https://docs.rs/ink_storage_traits/4.0.0-rc/ink_storage_traits/struct.AutoKey.html)
+[`AutoKey`](https://docs.rs/ink_storage_traits/4.0.0/ink_storage_traits/struct.AutoKey.html)
 primitive. They'll be generated at compile time and ruled out for conflicts.
 However, for non-`Packed` types like `Lazy` or the `Mapping`, the
-[`ManualKey`](https://docs.rs/ink_storage_traits/4.0.0-rc/ink_storage_traits/struct.ManualKey.html)
+[`ManualKey`](https://docs.rs/ink_storage_traits/4.0.0/ink_storage_traits/struct.ManualKey.html)
 primitive allows manual control over the storage key of a field like so:
 
 ```rust
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/faq/faq.md b/i18n/es/docusaurus-plugin-content-docs/current/faq/faq.md
index 56f468f449..760462d989 100644
--- a/i18n/es/docusaurus-plugin-content-docs/current/faq/faq.md
+++ b/i18n/es/docusaurus-plugin-content-docs/current/faq/faq.md
@@ -86,7 +86,7 @@ Mira la sección de las [Chain Extensions](/macros-attributes/chain-extension) p
 
 ### ¿Como puedo utilizar ink! en una cadena de Substrate con una configuración de cadena presonalizada?
 
-Pr favor mira [el argumento `env_types`](https://docs.rs/ink_macro/4.0.0-rc/ink_macro/attr.contract.html#header-arguments)
+Pr favor mira [el argumento `env_types`](https://docs.rs/ink_macro/4.0.0/ink_macro/attr.contract.html#header-arguments)
 para el macro del contrato. Te permite especificar el entorno en la 
 `#[ink::contract(env = MyEnvironment)]`.
 
@@ -161,15 +161,15 @@ La libreria estándar de Rust consiste en tres diferentes capas:
 
 Una serie de hashes criptográficos están integrados en el [contracts-pallet](/how-it-works) y
 por lo tanto son muy eficientes de utilizar. Actualmente soportamos un puñado de esos, puedes
-ver la lista completa [aquí](https://docs.rs/ink_env/4.0.0-rc/ink_env/hash/trait.CryptoHash.html).
+ver la lista completa [aquí](https://docs.rs/ink_env/4.0.0/ink_env/hash/trait.CryptoHash.html).
 
 Si necesitas utilizar urgentemente otro hash criptográfico puedes introducirlo a través de
 [Chain Extensions](/macros-attributes/chain-extension)
 o crear una propuesta para incluirlo en el conjunto por defecto de `contracts-pallet`.
 
 Se puede utilizar uno de los hashes criptográficos que ya están integrados como se explica aqui:
-* [`self.env().hash_bytes()`](https://docs.rs/ink_env/4.0.0-rc/ink_env/fn.hash_bytes.html)
-* [`self.env().hash_encoded()`](https://docs.rs/ink_env/4.0.0-rc/ink_env/fn.hash_encoded.html)
+* [`self.env().hash_bytes()`](https://docs.rs/ink_env/4.0.0/ink_env/fn.hash_bytes.html)
+* [`self.env().hash_encoded()`](https://docs.rs/ink_env/4.0.0/ink_env/fn.hash_encoded.html)
 
 ### ¿Por qué no es posible utilizar tipos de datos de coma flotante en ink!? ¿Cómo implemenar el retorno de un número decimal?
 
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/intro/intro.mdx b/i18n/es/docusaurus-plugin-content-docs/current/intro/intro.mdx
index c7c3446bbd..ee554e6b1d 100644
--- a/i18n/es/docusaurus-plugin-content-docs/current/intro/intro.mdx
+++ b/i18n/es/docusaurus-plugin-content-docs/current/intro/intro.mdx
@@ -21,11 +21,6 @@ hide_table_of_contents: false
     <a href="https://twitter.com/ink_lang">
         <img style={{height: 25}} src="https://img.shields.io/twitter/follow/ink_lang?label=Follow" />
     </a>
-    <br/>
-    <em>
-    ink! 4.0 fue publicado como versión candidata el 31 de Enero del 23.<br/>
-    Próximamente publicaremos la versión final.
-    </em>
 </center>
 
 <h3 style={{lineHeight: 1.4 + "em", marginTop: 0.5 + "em"}}>

From 75b852172a57c63095800f7a06060641465e9546 Mon Sep 17 00:00:00 2001
From: Michael Mueller <mich@elmueller.net>
Date: Wed, 15 Feb 2023 18:22:06 +0100
Subject: [PATCH 2/2] Update links

---
 docs/datastructures/custom.md                                   | 2 +-
 .../current/datastructures/custom.md                            | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/datastructures/custom.md b/docs/datastructures/custom.md
index 860aad9287..1929a97f46 100644
--- a/docs/datastructures/custom.md
+++ b/docs/datastructures/custom.md
@@ -20,7 +20,7 @@ trait, so it can be SCALE
 and
 [`decoded`](https://docs.rs/parity-scale-codec/3.2.2/parity_scale_codec/trait.Decode.html).
 Additionally, the traits
-[`StorageLayout`](https://docs.rs/ink_storage/latest/ink_storage/traits/trait.StorageLayout.html)
+[`StorageLayout`](https://docs.rs/ink_storage_traits/4.0.0/ink_storage_traits/trait.StorageLayout.html)
 and [`TypeInfo`](https://docs.rs/scale-info/2.3.1/scale_info/trait.TypeInfo.html)
 are required as well. But don't worry, usually these traits can just be derived:
 
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/datastructures/custom.md b/i18n/es/docusaurus-plugin-content-docs/current/datastructures/custom.md
index e2a0279e76..e69f65aaac 100644
--- a/i18n/es/docusaurus-plugin-content-docs/current/datastructures/custom.md
+++ b/i18n/es/docusaurus-plugin-content-docs/current/datastructures/custom.md
@@ -24,7 +24,7 @@ trait, so it can be SCALE
 and
 [`decoded`](https://docs.rs/parity-scale-codec/3.2.2/parity_scale_codec/trait.Decode.html).
 Additionally, the traits
-[`StorageLayout`](https://docs.rs/ink_storage/latest/ink_storage/traits/trait.StorageLayout.html)
+[`StorageLayout`](https://docs.rs/ink_storage_traits/4.0.0/ink_storage_traits/trait.StorageLayout.html)
 and [`TypeInfo`](https://docs.rs/scale-info/2.3.1/scale_info/trait.TypeInfo.html)
 are required as well. But don't worry, usually these traits can just be derived: