Skip to content

Commit 683084c

Browse files
GermanHCastano
authored andcommitted
Update README.md (#1521)
1 parent cde5a33 commit 683084c

File tree

5 files changed

+11
-12
lines changed

5 files changed

+11
-12
lines changed

CHANGELOG.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -690,9 +690,9 @@ ink! 3.0-rc4 is compatible with
690690
- [`substrate-contracts-node`](https://github.com/paritytech/substrate-contracts-node) version `0.1.0` or newer.
691691
- Install the newest version using `cargo install contracts-node --git https://github.com/paritytech/substrate-contracts-node.git --force`.
692692

693-
The documentation on our [Documentation Portal](https://ink.substrate.io)
693+
The documentation on our [Documentation Portal](https://use.ink)
694694
is up-to-date with this release candidate. Since the last release candidate we notably
695-
added a number of [Frequently Asked Questions](https://ink.substrate.io/faq)
695+
added a number of [Frequently Asked Questions](https://use.ink/faq)
696696
there.
697697

698698
### Quality Assurance
@@ -721,7 +721,7 @@ of key improvements to our testing setup:
721721
- Implemented the (unstable) `seal_rent_status` API ‒ [#798](https://github.com/paritytech/ink/pull/798).
722722
- Implemented the (unstable) `seal_debug_message` API ‒ [#792](https://github.com/paritytech/ink/pull/792).
723723
- Printing debug messages can now be achieved via `ink_env::debug_println!(…)`.
724-
- See [our documentation](https://ink.substrate.io/faq#how-do-i-print-something-to-the-console-from-the-runtime)
724+
- See [our documentation](https://use.ink/faq#how-do-i-print-something-to-the-console-from-the-runtime)
725725
for more information.
726726
- The examples have been updated to reflect this new way of printing debug messages.
727727
- Added usage comments with code examples to the `ink_env` API ‒ [#797](https://github.com/paritytech/ink/pull/797).
@@ -782,7 +782,7 @@ ink! 3.0-rc3 is compatible with
782782
### Added
783783

784784
- Implemented chain extensions feature for ink!.
785-
- ink!'s official documentation portal: https://ink.substrate.io/
785+
- ink!'s official documentation portal: https://use.ink/
786786
- It is now possible to pass a `salt` argument to contract instantiations.
787787
- Implemented fuzz testing for the ink! codebase.
788788

MONTHLY_UPDATE.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,3 @@
11
# Monthly Update: Parity Smart Contracts
22

3-
The monthly update has been moved to [https://ink.substrate.io/monthly-update](https://ink.substrate.io/monthly-update)!
3+
The monthly update has been moved to [https://use.ink/monthly-update](https://use.ink/monthly-update)!

README.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@
3434
<br/>
3535

3636
[Guided Tutorial for Beginners](https://docs.substrate.io/tutorials/smart-contracts/)&nbsp;&nbsp;&nbsp;&nbsp;
37-
[ink! Documentation Portal](https://ink.substrate.io)&nbsp;&nbsp;&nbsp;&nbsp;
37+
[ink! Documentation Portal](https://use.ink)&nbsp;&nbsp;&nbsp;&nbsp;
3838
[Developer Documentation](https://paritytech.github.io/ink/ink)
3939

4040

@@ -72,11 +72,10 @@ More relevant links:
7272
If you want to have a local setup you can use our [`substrate-contracts-node`](https://github.com/paritytech/substrate-contracts-node) for a quickstart.
7373
It's a simple Substrate blockchain which includes the Substrate module for smart contract functionality ‒ the `contracts` pallet (see [How it Works](#how-it-works) for more).
7474

75-
We also have a live testnet on [Rococo](https://github.com/paritytech/cumulus/#rococo-)
76-
called [Canvas](https://ink.substrate.io/canvas). Canvas is a Substrate based
75+
We also have a live testnet on [Rococo](https://github.com/paritytech/cumulus/#rococo-). Rococo is a Substrate based
7776
parachain which supports ink! smart contracts. For further instructions on using this
7877
testnet, follow the instructions in the
79-
[our documentation](https://ink.substrate.io/canvas#rococo-deployment).
78+
[our documentation](https://use.ink/testnet).
8079

8180
For both types of chains the [Contracts UI](https://contracts-ui.substrate.io/)
8281
can be used to instantiate your contract to a chain and interact with it.
@@ -245,7 +244,7 @@ The `#[ink::test]` procedural macro enables off-chain testing. See e.g. the [`ex
245244

246245
## Developer Documentation
247246

248-
We have [a very comprehensive documentation portal](https://ink.substrate.io),
247+
We have [a very comprehensive documentation portal](https://use.ink),
249248
but if you are looking for the crate level documentation itself, then these are
250249
the relevant links:
251250

examples/delegator/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ In order to test this bundle of smart contracts you need to execute the
1313
following steps.
1414

1515
You can upload the contracts using our [Contracts UI](https://contracts-ui.substrate.io/).
16-
If you want to test it locally, our [`substrate-contracts-node`](https://ink.substrate.io/getting-started/setup/#installing-the-substrate-smart-contracts-node)
16+
If you want to test it locally, our [`substrate-contracts-node`](https://use.ink/getting-started/setup/#installing-the-substrate-smart-contracts-node)
1717
is an easy way to get a local smart contract chain running.
1818

1919
1. Compile all contracts using the `./build-all.sh` script.

examples/rand-extension/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44

55
It demonstrates how to call a custom Substrate function from ink!.
66

7-
See [this chapter](https://ink.substrate.io/macros-attributes/chain-extension)
7+
See [this chapter](https://use.ink/macros-attributes/chain-extension)
88
in our ink! documentation for more details.
99

1010
There are two parts to this example:

0 commit comments

Comments
 (0)