Update Subnomicon links to go to Academy #530
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for subspace-docs-staging ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
jim-counter
requested changes
Jun 12, 2024
docs/farming-&-staking/farming/advanced-cli/cli-install.mdx
Outdated
Show resolved
Hide resolved
versioned_docs/version-latest/farming-&-staking/farming/advanced-cli/cli-install.mdx
Outdated
Show resolved
Hide resolved
| - [Plotting](https://subnomicon.subspace.network/docs/consensus/consensus/plotting) | ||
| - [Farming](https://subnomicon.subspace.network/docs/consensus/consensus/farming) | ||
| For more information about the principles of farming on the Subspace Network, you can still refer to the Autonpmys Academy links below: | ||
| - [Synchronization](https://academy.autonomys.net/subspace-protocol/network-architecture/networking-protocols#synchronization) |
There was a problem hiding this comment.
These bullets look better for the list of links. Maybe apply this approach to the lists of links everywhere in this update.
| [Plotting](https://subnomicon.subspace.network/docs/consensus/consensus/plotting) | ||
| [Farming](https://subnomicon.subspace.network/docs/consensus/consensus/farming) | ||
| If you would like to learn more about how the syncing, plotting and farming processes works on the Subspace Network, please refer to our Autonomys Academy links below. | ||
| [Synchronization](https://academy.autonomys.net/subspace-protocol/network-architecture/networking-protocols#synchronization) |
| @@ -97,5 +97,5 @@ The nomination pools in Subspace are "lazy": any fees earned by the operator are | |||
| Stake epoch is a designated period in domain blocks within a blockchain system that marks each stake allocation re-adjustment period. Occurring every `StakeEpochDuration` blocks (at the moment, it's set to every 100 blocks or ~10 minutes), an epoch transition triggers specific actions such as finalizing operator domain switches, deregistering operators, unlocking operators and their associated funds, and recalculating stake distribution for the Verifiable Random Function (VRF) election. These transitions are designed to adjust the stake distribution dynamically, finalize various staking-related operations, process rewards, and manage deposits and withdrawals. The uniform duration across all domains helps maintain consistency in the network, while the specific starting point for each domain's epoch transition may vary based on when it is registered, helping to amortize the load of these transitions. | |||
|
|
|||
| :::note | |||
| Read [Subspace Subnomicon](https://subnomicon.subspace.network/docs/category/decoupled-execution) to get a full picture behind decoupled execution! | |||
| Read [Autonomys Academy](https://academy.autonomys.net/subspace-protocol/decoupled-execution) to get a full picture behind decoupled execution! | |||
There was a problem hiding this comment.
Suggested change
| Read [Autonomys Academy](https://academy.autonomys.net/subspace-protocol/decoupled-execution) to get a full picture behind decoupled execution! | |
| Read the [Autonomys Academy](https://academy.autonomys.net/subspace-protocol/decoupled-execution) to get a full picture behind decoupled execution! |
versioned_docs/version-latest/farming-&-staking/farming/pulsar.mdx
Outdated
Show resolved
Hide resolved
| [Plotting](https://subnomicon.subspace.network/docs/consensus/consensus/plotting) | ||
| [Farming](https://subnomicon.subspace.network/docs/consensus/consensus/farming) | ||
| If you would like to learn more about how the syncing, plotting and farming processes works on the Subspace Network, please refer to our Autonomys Academy links below. | ||
| [Synchronization](https://academy.autonomys.net/subspace-protocol/network-architecture/networking-protocols#synchronization) |
| @@ -97,5 +97,5 @@ The nomination pools in Subspace are "lazy": any fees earned by the operator are | |||
| Stake epoch is a designated period in domain blocks within a blockchain system that marks each stake allocation re-adjustment period. Occurring every `StakeEpochDuration` blocks (at the moment, it's set to every 100 blocks or ~10 minutes), an epoch transition triggers specific actions such as finalizing operator domain switches, deregistering operators, unlocking operators and their associated funds, and recalculating stake distribution for the Verifiable Random Function (VRF) election. These transitions are designed to adjust the stake distribution dynamically, finalize various staking-related operations, process rewards, and manage deposits and withdrawals. The uniform duration across all domains helps maintain consistency in the network, while the specific starting point for each domain's epoch transition may vary based on when it is registered, helping to amortize the load of these transitions. | |||
|
|
|||
| :::note | |||
| Read [Subspace Subnomicon](https://subnomicon.subspace.network/docs/category/decoupled-execution) to get a full picture behind decoupled execution! | |||
| Read [Autonomys Academy](https://academy.autonomys.net/subspace-protocol/decoupled-execution) to get a full picture behind decoupled execution! | |||
There was a problem hiding this comment.
Suggested change
| Read [Autonomys Academy](https://academy.autonomys.net/subspace-protocol/decoupled-execution) to get a full picture behind decoupled execution! | |
| Read the [Autonomys Academy](https://academy.autonomys.net/subspace-protocol/decoupled-execution) to get a full picture behind decoupled execution! |
Apply Jim's suggestions Co-authored-by: Jim Counter <jimcounter@hotmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.