diff --git a/docs/build/guides/mobile/react-native-quickstart.md b/docs/build/guides/mobile/react-native-quickstart.md index 2d41f23dc2..6d2c88c74c 100644 --- a/docs/build/guides/mobile/react-native-quickstart.md +++ b/docs/build/guides/mobile/react-native-quickstart.md @@ -299,7 +299,7 @@ In the `args` section, we are simply passing it our user's account address from Go ahead and click the "Send Query" button. You should see "No Profile." That's because we haven't initialized the account yet. -## Initializing the Account +## Initializing an Account For the Profile contract to store a Profile in a user's account, it does so by initializing what is called a "resource." A resource is an ownable piece of data and functionality that can live in the user's account storage. This paradigm is known is as "resource-oriented-programming", a principle that is core to Cadence and differentiates its ownership model from other smart contract languages, [read more here](../../smart-contracts/cadence.md#intuiting-ownership-with-resources). Cadence makes it so that resources can only exist in one place at any time, they must be deliberately created, cannot be copied, and if desired, must be deliberately destroyed. diff --git a/docs/networks/node-ops/node-operation/guides/genesis-bootstrap.md b/docs/networks/node-ops/node-operation/guides/genesis-bootstrap.md index c7b724aad0..186a7c7bf1 100644 --- a/docs/networks/node-ops/node-operation/guides/genesis-bootstrap.md +++ b/docs/networks/node-ops/node-operation/guides/genesis-bootstrap.md @@ -20,7 +20,7 @@ The Flow consensus algorithm depends on there always being a previous block, whi The bootstrapping process will be in 2 phases, with the Flow team signing the Genesis block between the two. - The bootstrapping process deals with a number of different keys. Make sure you understand their usage and terminology by reviewing the [Node Keys Guide](../node-bootstrap.md#generating-your-node-id). + The bootstrapping process deals with a number of different keys. Make sure you understand their usage and terminology by reviewing the [Node Keys Guide](../node-bootstrap.md#generating-your-node-keys). ## Download the Bootstrapping Toolkit diff --git a/docs/networks/node-ops/node-operation/spork.md b/docs/networks/node-ops/node-operation/spork.md index 4b89a9e0c7..8d2210bb7e 100644 --- a/docs/networks/node-ops/node-operation/spork.md +++ b/docs/networks/node-ops/node-operation/spork.md @@ -87,9 +87,3 @@ See [Node Bootstrap](./node-bootstrap.md) for detailed information on Docker/Sys ``` This error is OK. Your fellow node operators have not turned on/joined the network yet. So no need to worry about it! - -### Flow Node Not Booting Up - -If your Flow node is not able to boot up, or it exits right after it boots up. You will need to do a [clean up of your state](./node-bootstrap.md#step-0---cleaning-up-your-previous-state). - -After cleaning up the state try booting it up again. If the problem persists, message a member from the Flow team on Discord.