You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/md/en/docs/test/set-up-a-test-network.md
+3-2
Original file line number
Diff line number
Diff line change
@@ -53,7 +53,7 @@ To prepare a working folder with the binaries for the test network:
53
53
Release branches use the naming convention `release-v<n.n.n>`.
54
54
For example, the release branch used in this tutorial is `release-v1.0.0`.
55
55
You can check out a more recent release branch instead of using `release-v1.0.0`.
56
-
You can find information about recent releases and what's included in each release on the [Releases](https://github.com/paritytech/polkadot/releases) tab.
56
+
You can find information about recent releases and what's included in each release on the [Releases](https://github.com/paritytech/polkadot-sdk/releases) tab.
57
57
58
58
1. Change to the root of the `polkadot` directory by running the following command:
59
59
@@ -69,10 +69,11 @@ To prepare a working folder with the binaries for the test network:
69
69
70
70
Compiling the node can take 15 to 60 minuets to complete.
71
71
72
-
1. Copy the Polkadot binary into your working `bin` folder by running a command similar to the following:
72
+
1. Copy the Polkadot binary and workers into your working `bin` folder by running a command similar to the following:
As this example illustrates, it's generally a good practice to append the version of `polkadot` to the binary name to keep the files in the `bin` folder organized.
0 commit comments