chore: update refs to Use Ink (#342)

* chore: update GitHub links to use-ink

* chore: update email to [email protected] and org name

* chore: update from Parity's ink!

* chore: update contracts-ui links

* fix: docusaurus field organizatioName to proper GitHub user

* chore: update wording in all version of CosmWasm guide

---------

Co-authored-by: Michael Müller <[email protected]>

Author: peterwht

README.md

@@ -1,6 +1,6 @@
 # `ink-docs`
 
-This is the documentation portal for [ink!](https://github.com/paritytech/ink). The latest version is always available at [https://use.ink](https://use.ink).
+This is the documentation portal for [ink!](https://github.com/use-ink/ink). The latest version is always available at [https://use.ink](https://use.ink).
 
 Run it locally via
 
@@ -15,8 +15,8 @@ yarn start --locale es
 We want to provide comprehensive documentation for anything you need to work with ink! here.
 
 If you spot gaps in the information provided, or are uncertain about any
-specific area, please do <a href="https://github.com/paritytech/ink-docs/issues">log an issue</a>
-or <a href="https://github.com/paritytech/ink-docs/pulls">make a pull-request</a>.
+specific area, please do <a href="https://github.com/use-ink/ink-docs/issues">log an issue</a>
+or <a href="https://github.com/use-ink/ink-docs/pulls">make a pull-request</a>.
 
 We really want to have good documentation here and allow people to be productive
 right from the start.

docs/basics/cross-contract-calling.md

@@ -34,7 +34,7 @@ If you want to interact with a contract that is already on-chain you will need t
 
 ### `BasicContractRef` walkthrough
 
-We will walk through the [`cross-contract-calls`](https://github.com/paritytech/ink-examples/tree/master/cross-contract-calls)
+We will walk through the [`cross-contract-calls`](https://github.com/use-ink/ink-examples/tree/master/cross-contract-calls)
 example in order to demonstrate how cross-contract calls using contract references work.
 
 The general workflow will be:

docs/basics/environment.md

@@ -14,8 +14,8 @@ Substrate types, you have to make sure to configure that chain's
 `Environment` for your contract!
 :::
 
-ink! defines a trait [`Environment`](https://paritytech.github.io/ink/ink_env/trait.Environment.html)
-and also a default implementation of that trait ‒ [`DefaultEnvironment`](https://paritytech.github.io/ink/ink_env/enum.DefaultEnvironment.html).
+ink! defines a trait [`Environment`](https://use-ink.github.io/ink/ink_env/trait.Environment.html)
+and also a default implementation of that trait ‒ [`DefaultEnvironment`](https://use-ink.github.io/ink/ink_env/enum.DefaultEnvironment.html).
 
 These are the types that ink! uses, if no explicit steps are taken:
 
@@ -49,7 +49,7 @@ type as Ethereum for their `AccountId`.
 
 Most Substrate chains stay with the default Substrate types though and
 ink! just uses those by default as well. It is possible to configure
-a different environment in the contract macro ([documentation here](https://paritytech.github.io/ink/ink/attr.contract.html#header-arguments))
+a different environment in the contract macro ([documentation here](https://use-ink.github.io/ink/ink/attr.contract.html#header-arguments))
 though:
 
 ```rust

docs/basics/events.md

@@ -57,7 +57,7 @@ mod erc20 {
 }
 ```
 
-See our [`ERC20 example contract`](https://github.com/paritytech/ink-examples/blob/main/erc20/lib.rs) 
+See our [`ERC20 example contract`](https://github.com/use-ink/ink-examples/blob/main/erc20/lib.rs) 
 for an elaborate example which uses events.
 
 ## Event Definition
@@ -82,7 +82,7 @@ pub struct Transferred {
     amount: u128,
 }
 ```
-> Note that generics are [not currently supported](https://github.com/paritytech/ink/issues/2044)
+> Note that generics are [not currently supported](https://github.com/use-ink/ink/issues/2044)
 > , so the concrete types of `Environment` 
 > specific types such as `AccountId` must match up with the types used in the contract.
 

docs/basics/metadata.md

@@ -87,7 +87,7 @@ It may _optionally_ include the following keys:
 :::info
 
 If you're interested in the code reference from `cargo-contract`
-see [here](https://github.com/paritytech/cargo-contract/blob/30ba1ec545d01c0479fe47c97d2c8911ab868d46/crates/metadata/src/lib.rs#L157).
+see [here](https://github.com/use-ink/cargo-contract/blob/30ba1ec545d01c0479fe47c97d2c8911ab868d46/crates/metadata/src/lib.rs#L157).
 
 :::
 
@@ -111,15 +111,15 @@ It can _optionally_ include the following keys:
   "name": "flipper",
   "version": "4.0.0-beta.1",
   "authors": [
-    "Parity Technologies <[email protected]>"
+    "Use Ink <[email protected]>"
   ]
 }
 ```
 
 :::info
 
 If you're interested in the code reference from `cargo-contract`
-see [here](https://github.com/paritytech/cargo-contract/blob/30ba1ec545d01c0479fe47c97d2c8911ab868d46/crates/metadata/src/lib.rs#L432).
+see [here](https://github.com/use-ink/cargo-contract/blob/30ba1ec545d01c0479fe47c97d2c8911ab868d46/crates/metadata/src/lib.rs#L432).
 
 :::
 
@@ -149,7 +149,7 @@ The ink! metadata consists of the following **required** sections
 :::info
 
 If you're interested in the code reference from `ink!`
-see [here](https://github.com/paritytech/ink/blob/c8aa3ee41112b327d4f3cb3959f188945c8ccace/crates/metadata/src/lib.rs#L90).
+see [here](https://github.com/use-ink/ink/blob/c8aa3ee41112b327d4f3cb3959f188945c8ccace/crates/metadata/src/lib.rs#L90).
 
 :::
 

docs/basics/trait-definitions.md

@@ -11,7 +11,7 @@ Through the `#[ink::trait_definition]` proc. macro it is now possible to define
 This allows to define shared smart contract interfaces to different concrete implementations.
 Note that this ink! trait definition can be defined anywhere, even in another crate!
 
-See our [`ERC20-Trait example contract`](https://github.com/paritytech/ink-examples/blob/main/trait-erc20/lib.rs) 
+See our [`ERC20-Trait example contract`](https://github.com/use-ink/ink-examples/blob/main/trait-erc20/lib.rs) 
 for an elaborate example which uses trait definitions.
 
 ### Example

docs/basics/upgradeability.md

@@ -278,7 +278,7 @@ self.env().lock_delegate_dependency(&code_hash);
 
 Note that these two methods can be called by anybody executing the contract, so it is the 
 responsibility of the contract developer to ensure correct access control.
-You can take a look at our [`upgradeable-contracts/delegator`](https://github.com/paritytech/ink-examples/tree/main/upgradeable-contracts#delegator)
+You can take a look at our [`upgradeable-contracts/delegator`](https://github.com/use-ink/ink-examples/tree/main/upgradeable-contracts#delegator)
 example, which demonstrates the usage of these two functions.
 
 ## Note on the usage of wildcard selectors
@@ -290,12 +290,12 @@ Since ink! 5 we have restricted the usage of the wildcard selector due to
 [security reasons](https://blog.openzeppelin.com/security-review-ink-cargo-contract#custom-selectors-could-facilitate-proxy-selector-clashing-attacks).
 
 :::danger Beware
-Due to [IIP-2](https://github.com/paritytech/ink/issues/1676), ink! only allows
+Due to [IIP-2](https://github.com/use-ink/ink/issues/1676), ink! only allows
 to contain a single message with a well-known selector `@` when the other message
 with the wildcard selector `_` is defined.
 :::
 
-See [example](https://github.com/paritytech/ink-examples/tree/main/wildcard-selector)
+See [example](https://github.com/use-ink/ink-examples/tree/main/wildcard-selector)
 for illustration on how it can be used in practice.
 
 ## Note on `CallFlags`
@@ -314,7 +314,7 @@ Some useful properties:
 
 Following [Substrate's runtime upgradeability](https://docs.substrate.io/maintain/runtime-upgrades/) 
 philosophy, ink! also supports an easy way to update your contract code via the special function 
-[`set_code_hash()`](https://paritytech.github.io/ink/ink_env/fn.set_code_hash.html).
+[`set_code_hash()`](https://use-ink.github.io/ink/ink_env/fn.set_code_hash.html).
 
 ### Properties
 
@@ -426,4 +426,4 @@ for more details.
 ## Examples
 
 Examples of upgradable contracts can be found in the 
-[ink! repository](https://github.com/paritytech/ink-examples/tree/main/upgradeable-contracts).
+[ink! repository](https://github.com/use-ink/ink-examples/tree/main/upgradeable-contracts).

docs/basics/verification/contract-verification.md

@@ -55,7 +55,7 @@ It should contain a key-value `image` after the `contract` information:
     "name": "flipper",
     "version": "4.3.0",
     "authors": [
-      "Parity Technologies <[email protected]>"
+      "Use Ink <[email protected]>"
     ]
   },
   "image": "paritytech/contracts-verifiable:4.0.0-alpha",
@@ -118,4 +118,4 @@ of all contracts to be visible. Specify a relative manifest path to the root con
 :::
 
 You can find a Dockerfile and further documentation on image usage 
-in [the `cargo-contract` repository](https://github.com/paritytech/cargo-contract/tree/master/build-image)
+in [the `cargo-contract` repository](https://github.com/use-ink/cargo-contract/tree/master/build-image)

docs/brand-assets/cargo-contract.md

@@ -6,7 +6,7 @@ hide_table_of_contents: true
 
 ## `cargo-contract` Logo
 
-The following is the logo for our command-line tool [`cargo-contract`](https://github.com/paritytech/cargo-contract).
+The following is the logo for our command-line tool [`cargo-contract`](https://github.com/use-ink/cargo-contract).
 
 <div className="black-container">
     <img src="/img/cargo-contract-logo.svg" alt="cargo-contract logo" className="brand-asset" />

docs/brand-assets/community-badges.md

@@ -10,33 +10,33 @@ if you could add one of those!
 ## Built _with_ ink!
 ### Normal Design
 
-[![Built with ink!](https://raw.githubusercontent.com/paritytech/ink/master/.images/badge.svg)](https://github.com/paritytech/ink)
+[![Built with ink!](https://raw.githubusercontent.com/use-ink/ink/master/.images/badge.svg)](https://github.com/use-ink/ink)
 
 ```markdown
-[![Built with ink!](https://raw.githubusercontent.com/paritytech/ink/master/.images/badge.svg)](https://github.com/paritytech/ink)
+[![Built with ink!](https://raw.githubusercontent.com/use-ink/ink/master/.images/badge.svg)](https://github.com/use-ink/ink)
 ```
 
 ### Flat Design
 
-[![Built with ink!](https://raw.githubusercontent.com/paritytech/ink/master/.images/badge_flat.svg)](https://github.com/paritytech/ink)
+[![Built with ink!](https://raw.githubusercontent.com/use-ink/ink/master/.images/badge_flat.svg)](https://github.com/use-ink/ink)
 
 ```markdown
-[![Built with ink!](https://raw.githubusercontent.com/paritytech/ink/master/.images/badge_flat.svg)](https://github.com/paritytech/ink)
+[![Built with ink!](https://raw.githubusercontent.com/use-ink/ink/master/.images/badge_flat.svg)](https://github.com/use-ink/ink)
 ```
 
 ## Built _for_ ink!
 ### Normal Design
 
-[![Built with ink!](https://raw.githubusercontent.com/paritytech/ink/master/.images/built-for-ink.svg)](https://github.com/paritytech/ink)
+[![Built with ink!](https://raw.githubusercontent.com/use-ink/ink/master/.images/built-for-ink.svg)](https://github.com/use-ink/ink)
 
 ```markdown
-[![Built with ink!](https://raw.githubusercontent.com/paritytech/ink/master/.images/built-for-ink.svg)](https://github.com/paritytech/ink)
+[![Built with ink!](https://raw.githubusercontent.com/use-ink/ink/master/.images/built-for-ink.svg)](https://github.com/use-ink/ink)
 ```
 
 ### Flat Design
 
-[![Built with ink!](https://raw.githubusercontent.com/paritytech/ink/master/.images/built-for-ink-flat.svg)](https://github.com/paritytech/ink)
+[![Built with ink!](https://raw.githubusercontent.com/use-ink/ink/master/.images/built-for-ink-flat.svg)](https://github.com/use-ink/ink)
 
 ```markdown
-[![Built with ink!](https://raw.githubusercontent.com/paritytech/ink/master/.images/built-for-ink-flat.svg)](https://github.com/paritytech/ink)
+[![Built with ink!](https://raw.githubusercontent.com/use-ink/ink/master/.images/built-for-ink-flat.svg)](https://github.com/use-ink/ink)
 ```

docs/datastructures/storage-layout.md

@@ -62,7 +62,7 @@ number of elements, instead.
 ## Eager Loading vs. Lazy Loading
 ink! provides means of breaking the storage up into smaller pieces, which can be loaded
 on demand, with the
-[`Lazy`](https://paritytech.github.io/ink/ink/storage/struct.Lazy.html) primitive.
+[`Lazy`](https://use-ink.github.io/ink/ink/storage/struct.Lazy.html) primitive.
 Wrapping any storage field inside a `Lazy` struct makes the storage
 struct in which that field appears also
 non-`Packed`, preventing it from being eagerly loaded during arbitrary storage operations:

docs/datastructures/storagevec.md

@@ -84,7 +84,7 @@ This can be undesirable:
 The cost of reading or writing a _single_ element grows linearly
 corresponding to the number of elements in the vector (its length).
 Additionally, the maximum capacity of the _whole_ vector is limited by
-the size of [ink!'s static buffer](https://github.com/paritytech/ink/blob/master/ARCHITECTURE.md#communication-with-the-pallet)
+the size of [ink!'s static buffer](https://github.com/use-ink/ink/blob/master/ARCHITECTURE.md#communication-with-the-pallet)
 used during ABI encoding and decoding (default 16 KiB).
 
 `StorageVec` on the other hand allows to access each element individually.

docs/examples/contracts.md

@@ -8,31 +8,31 @@ hide_title: true
 
 # Smart Contract Examples
 
-We have a repository <a href="https://github.com/paritytech/ink-examples/tree/main">`ink-examples`</a>,
+We have a repository <a href="https://github.com/use-ink/ink-examples/tree/main">`ink-examples`</a>,
 in which you find a number of contracts written in ink!.
 Some of the most interesting ones:
 
 <div className="row">
     <div className="col text--center">
-        <a href="https://github.com/paritytech/ink-examples/tree/main/flipper"><img src="/img/icons/flipper.svg" width="100" /></a>
+        <a href="https://github.com/use-ink/ink-examples/tree/main/flipper"><img src="/img/icons/flipper.svg" width="100" /></a>
         <p>
             Our "Hello, World!".<br/>
-            <a href="https://github.com/paritytech/ink-examples/tree/main/flipper">» view example</a>
+            <a href="https://github.com/use-ink/ink-examples/tree/main/flipper">» view example</a>
         </p>
     </div>
     <div className="col text--center">
-        <a href="https://github.com/paritytech/ink-examples/tree/main/erc20"><img src="/img/icons/erc20.svg" width="100" /></a>
+        <a href="https://github.com/use-ink/ink-examples/tree/main/erc20"><img src="/img/icons/erc20.svg" width="100" /></a>
         <p>
             An ERC-20 implementation.<br/>
-            <a href="https://github.com/paritytech/ink-examples/tree/main/erc20">» view example</a>
+            <a href="https://github.com/use-ink/ink-examples/tree/main/erc20">» view example</a>
         </p>
     </div>
     <div className="col text--center">
-        <a href="https://github.com/paritytech/ink-examples/tree/main/erc721"><img src="/img/icons/nft.svg" width="100" /></a>
+        <a href="https://github.com/use-ink/ink-examples/tree/main/erc721"><img src="/img/icons/nft.svg" width="100" /></a>
         <p>
-            <a href="https://github.com/paritytech/ink-examples/tree/main/erc721">» view ERC-721</a>
+            <a href="https://github.com/use-ink/ink-examples/tree/main/erc721">» view ERC-721</a>
             <br/>
-            <a href="https://github.com/paritytech/ink-examples/tree/main/erc1155">» view ERC-1155</a>
+            <a href="https://github.com/use-ink/ink-examples/tree/main/erc1155">» view ERC-1155</a>
         </p>
     </div>
 </div>
@@ -41,24 +41,24 @@ Some of the most interesting ones:
 
 <div className="row">
     <div className="col text--center">
-        <a href="https://github.com/paritytech/ink-examples/tree/main/upgradeable-contracts"><img src="/img/icons/upgradable.svg" width="100" /></a>
+        <a href="https://github.com/use-ink/ink-examples/tree/main/upgradeable-contracts"><img src="/img/icons/upgradable.svg" width="100" /></a>
         <p>
             An upgradeable contract.<br/>
-            <a href="https://github.com/paritytech/ink-examples/tree/main/upgradeable-contracts">» view example</a>
+            <a href="https://github.com/use-ink/ink-examples/tree/main/upgradeable-contracts">» view example</a>
         </p>
     </div>
     <div className="col text--center">
-        <a href="https://github.com/paritytech/ink-examples/tree/main/multisig"><img src="/img/icons/multisig.svg" width="100" /></a>
+        <a href="https://github.com/use-ink/ink-examples/tree/main/multisig"><img src="/img/icons/multisig.svg" width="100" /></a>
         <p>
             A multi-signature wallet.<br/>
-            <a href="https://github.com/paritytech/ink-examples/tree/main/multisig">» view example</a>
+            <a href="https://github.com/use-ink/ink-examples/tree/main/multisig">» view example</a>
         </p>
     </div>
     <div className="col text--center">
-        <a href="https://github.com/paritytech/ink-examples/tree/main/rand-extension"><img src="/img/icons/rand-extension.svg" width="100" /></a>
+        <a href="https://github.com/use-ink/ink-examples/tree/main/rand-extension"><img src="/img/icons/rand-extension.svg" width="100" /></a>
         <p>
             Allow runtime access.<br/>
-            <a href="https://github.com/paritytech/ink-examples/tree/main/rand-extension">» view example</a>
+            <a href="https://github.com/use-ink/ink-examples/tree/main/rand-extension">» view example</a>
         </p>
     </div>
 </div>
@@ -67,24 +67,24 @@ Some of the most interesting ones:
 
 <div className="row">
     <div className="col text--center">
-        <a href="https://github.com/paritytech/ink-examples/tree/main/upgradeable-contracts/delegator"><img src="/img/icons/delegator.svg" width="100" /></a>
+        <a href="https://github.com/use-ink/ink-examples/tree/main/upgradeable-contracts/delegator"><img src="/img/icons/delegator.svg" width="100" /></a>
         <p>
             Cross-contract calls.<br/>
-            <a href="https://github.com/paritytech/ink-examples/tree/main/upgradeable-contracts/delegator">» view example</a>
+            <a href="https://github.com/use-ink/ink-examples/tree/main/upgradeable-contracts/delegator">» view example</a>
         </p>
     </div>
     <div className="col text--center">
-        <a href="https://github.com/paritytech/ink-examples/tree/main/trait-erc20"><img src="/img/icons/trait-erc20.svg" width="100" /></a>
+        <a href="https://github.com/use-ink/ink-examples/tree/main/trait-erc20"><img src="/img/icons/trait-erc20.svg" width="100" /></a>
         <p>
             Implements an <code>Erc20</code> trait.<br/>
-            <a href="https://github.com/paritytech/ink-examples/tree/main/trait-erc20">» view example</a>
+            <a href="https://github.com/use-ink/ink-examples/tree/main/trait-erc20">» view example</a>
         </p>
     </div>
     <div className="col text--center">
-        <a href="https://github.com/paritytech/ink-examples/tree/main/dns"><img src="/img/icons/dns.svg" width="100" /></a>
+        <a href="https://github.com/use-ink/ink-examples/tree/main/dns"><img src="/img/icons/dns.svg" width="100" /></a>
         <p>
             Simple <code>DomainNameService</code>.<br/>
-            <a href="https://github.com/paritytech/ink-examples/tree/main/dns">» view example</a>
+            <a href="https://github.com/use-ink/ink-examples/tree/main/dns">» view example</a>
         </p>
     </div>
 </div>

docs/examples/dapps.md

@@ -32,7 +32,7 @@ link! is a URL shortener dApp. It consists of a frontend and an ink! contract.
 
 link! uses [`polkadot-js/api`](https://github.com/polkadot-js/api) under the hood.
 The entire source code (contract + frontend) is located here:
-[https://github.com/paritytech/link](https://github.com/paritytech/link).
+[https://github.com/use-ink/link](https://github.com/use-ink/link).
 
 You can view an online demo of the dApp here: [https://tiny.ink](https://tiny.ink).