updated env_template references in hornet and iota-core using_docker.…

…md (#1559) removed mouse hover on value transactions in hornet and iota-core welcome.md removed auto-peering port in iota-core getting_started.md fixed type in validator_setup.md updated text in step 4 of validator_setup.md updated iota-core version to 1.0
iotaledger · May 15, 2024 · d208958 · d208958
1 parent 613a0a3
commit d208958
Show file tree

Hide file tree

Showing 11 changed files with 8 additions and 14 deletions.
diff --git a/docs/maintain/hornet/2.0/docs/how_tos/post_installation.md b/docs/maintain/hornet/2.0/docs/how_tos/post_installation.md
@@ -57,12 +57,6 @@ To generate a JWT-token to be used with the protected routes you can run:
 
 If you are running our [recommended setup](using_docker.md) then see [here](using_docker.md#tools).
 
-### Proof-of-Work
-
-If you are concerned with resource consumption, consider turning off `restAPI.pow.enabled`.
-This way, the clients must perform proof of work locally before submitting a block for broadcast.
-If you would like to offer proof of work to clients, consider increasing the `restAPI.pow.workerCount` to provide a faster block submission experience.
-
 ### Reverse Proxy
 
 We recommend that you provide your HTTP REST API behind a reverse proxy, such as [HAProxy](http://www.haproxy.org/), [Traefik](https://traefik.io/), [Nginx](https://www.nginx.com/), or [Apache](https://www.apache.org/) configured with TLS.

diff --git a/docs/maintain/hornet/2.0/docs/welcome.md b/docs/maintain/hornet/2.0/docs/welcome.md
@@ -22,7 +22,7 @@ It provides the full node capabilities including full support of the latest netw
 By running your own node you have the following benefits:
 
 - You have direct access to the IOTA or Shimmer network, instead of having to connect to and trust someone else's node.
-- You help the network to become more distributed and resilient by validating blocks and _value transactions_.
+- You help the network to become more distributed and resilient by validating blocks and value transactions.
 
 ## Source Code
 

diff --git a/...0/docs/getting_started/getting_started.md → ...0/docs/getting_started/getting_started.md b/...0/docs/getting_started/getting_started.md → ...0/docs/getting_started/getting_started.md
@@ -33,7 +33,6 @@ database.
 IOTA-Core exposes different functionality on different ports:
 
 - `15600 TCP` - Gossip protocol port.
-- `14626 UDP` - Autopeering port (optional).
 - `14265 TCP` - REST HTTP API port (optional).
 
 These ports are essential for flawless node operation. The REST HTTP API port is optional and is only needed if

diff --git a/...ore/2.0/docs/how_tos/post_installation.md → ...ore/1.0/docs/how_tos/post_installation.md b/...ore/2.0/docs/how_tos/post_installation.md → ...ore/1.0/docs/how_tos/post_installation.md
diff --git a/...ota-core/2.0/docs/how_tos/using_docker.md → ...ota-core/1.0/docs/how_tos/using_docker.md b/...ota-core/2.0/docs/how_tos/using_docker.md → ...ota-core/1.0/docs/how_tos/using_docker.md
@@ -93,7 +93,7 @@ You can configure your node to either use HTTP or HTTPS. For publicly exposed no
 :::
 
 ```sh reference
-https://github.com/iotaledger/node-docker-setup/blob/feat/iota-core/testnet_iota-2.0/env_template
+https://github.com/iotaledger/node-docker-setup/blob/main/iota2-testnet/env_template
 ```
 
 ### 3. Setup neighbors

diff --git a/...-core/2.0/docs/how_tos/validator_setup.md → ...-core/1.0/docs/how_tos/validator_setup.md b/...-core/2.0/docs/how_tos/validator_setup.md → ...-core/1.0/docs/how_tos/validator_setup.md
@@ -45,7 +45,7 @@ command `echo 0xff`.
 
 ## Set Up the CLI Wallet
 
-### 1a. Downlaod the latest Version
+### 1a. Download the latest Version
 
 You can download the latest release of the CLI Wallet from the following link:
 https://github.com/iotaledger/iota-sdk/releases/tag/cli-wallet-v2.0.0-beta.2
@@ -163,9 +163,10 @@ implicit-accounts
 
 You should run this until the BIC changes from `None` to `Some(0)`, then copy the `Output Id`.
 
-### 4. Transition the Account
+### 4. Transition the Implicit Account to a Full Account
 
-You can transition your account by running the following command:
+You need to transition your implicit account to a full account to be able to become a validator by running the following
+command:
 
 ```bash
 implicit-account-transition {Output Id}

diff --git a/...core/2.0/docs/references/api_reference.md → ...core/1.0/docs/references/api_reference.md b/...core/2.0/docs/references/api_reference.md → ...core/1.0/docs/references/api_reference.md
diff --git a/...core/2.0/docs/references/configuration.md → ...core/1.0/docs/references/configuration.md b/...core/2.0/docs/references/configuration.md → ...core/1.0/docs/references/configuration.md
diff --git a/docs/maintain/iota-core/2.0/docs/welcome.md → docs/maintain/iota-core/1.0/docs/welcome.md b/docs/maintain/iota-core/2.0/docs/welcome.md → docs/maintain/iota-core/1.0/docs/welcome.md
@@ -19,7 +19,7 @@ It provides full-node capabilities, including full support for the latest networ
 By running your own node, you have the following benefits:
 
 - You have direct access to the IOTA network instead of having to connect to and trust someone else's node.
-- You help the network to become more distributed and resilient by validating blocks and _value transactions_.
+- You help the network to become more distributed and resilient by validating blocks and value transactions.
 
 ## Source Code
 

diff --git a/docs/maintain/iota-core/2.0/sidebars.js → docs/maintain/iota-core/1.0/sidebars.js b/docs/maintain/iota-core/2.0/sidebars.js → docs/maintain/iota-core/1.0/sidebars.js
diff --git a/versionedConfig.js b/versionedConfig.js
@@ -132,7 +132,7 @@ exports.maintainPluginsConfig = [
     subsection: 'maintain-layer-1',
     versions: [
       {
-        label: '2.0',
+        label: '1.0',
         badges: ['Testnet'],
       },
     ],