From 69002fddda81f12f9d3b49a3dcd1dea4db6cd410 Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Tue, 7 Nov 2023 15:33:23 -0500 Subject: [PATCH 1/4] Capitalize "Mainnet" --- docs/architecture/governance.md | 4 ++-- docs/dApps/best-practices.md | 2 +- docs/developing/dev-environments.md | 2 +- docs/developing/information/block-explorers.md | 2 +- .../block-explorers/inspect-contract-tzstats.md | 2 +- docs/developing/sandbox.md | 2 +- docs/tutorials/build-your-first-app/wallets-tokens.md | 2 +- docs/tutorials/create-an-nft/nft-taquito.md | 4 ++-- docs/tutorials/create-an-nft/nft-tznft.md | 4 ++-- docs/tutorials/smart-contract/archetype.md | 6 +++--- docs/tutorials/smart-contract/cameligo.md | 8 ++++---- docs/tutorials/smart-contract/jsligo.md | 8 ++++---- docs/tutorials/smart-contract/smartpy.md | 8 ++++---- 13 files changed, 27 insertions(+), 27 deletions(-) diff --git a/docs/architecture/governance.md b/docs/architecture/governance.md index 7f3d822b9..a0f693aa3 100644 --- a/docs/architecture/governance.md +++ b/docs/architecture/governance.md @@ -33,13 +33,13 @@ The voting participation target tries to match the exponential moving average of Previously, during the voting process, a test chain would be spun up during the “testing period” which took place between the exploration and promotion voting periods. The intent was that this test chain be used to verify that the new proposal worked correctly, but in practice, the test chain has never been used in this manner and has caused significant operational problems to node operators. -The Florence upgrade eliminates the test chain activation, the testing period has been retained but is now named the “cooldown period”. Instead, testing the protocol continues by using test chains that operate outside of the mainnet voting process. +The Florence upgrade eliminates the test chain activation, the testing period has been retained but is now named the “cooldown period”. Instead, testing the protocol continues by using test chains that operate outside of the Mainnet voting process. #### 4. Promotion Vote Period At the end of the Testing Period, the Promotion Vote Period begins. In this period, the network decides whether to adopt the amendment based on off-chain discussions and its behavior during the Testing Period. As in the Exploration Vote Period, bakers submit their votes using the ballot operation, with their votes weighted proportionally to the number of rolls in their staking balance. -At the end of the Promotion Vote Period, the network counts the number of votes. If the participation rate reaches the minimum quorum and an 80% supermajority of non-abstaining bakers votes “Yea,” then the proposal is activated as the new mainnet. Otherwise, the process once more reverts to the Proposal Period. The minimum vote participation rate is set based on past participation rates. +At the end of the Promotion Vote Period, the network counts the number of votes. If the participation rate reaches the minimum quorum and an 80% supermajority of non-abstaining bakers votes “Yea,” then the proposal is activated as the new Mainnet. Otherwise, the process once more reverts to the Proposal Period. The minimum vote participation rate is set based on past participation rates. See [the full details of the governance process](https://medium.com/tezos/amending-tezos-b77949d97e1e). diff --git a/docs/dApps/best-practices.md b/docs/dApps/best-practices.md index 409de3dfd..b35a27fce 100644 --- a/docs/dApps/best-practices.md +++ b/docs/dApps/best-practices.md @@ -24,7 +24,7 @@ Connecting and interacting with a wallet is an experience specific to web3 apps 1. **Do not force wallet connection**: the request to connect a user's wallet must come from the user interacting with your dapp, not appear out of nowhere, for example, when the dapp loads. Let the user get some details about your dapp before they decide to connect their wallet. 2. **Choose the right position for the wallet button**: the users visiting your dapp will expect to find the button to connect or interact with their wallet in the upper part of the interface, on the left or right side. The button must be clearly visible and discoverable in one second. -3. **Display wallet information**: the minimal information to display is the address of the connected account to let the users know which account they are using. A lot of dapps on Tezos also display the XTZ balance, as well as the network the dapp is connected to (mainnet/testnet) or the wallet used for the connection. +3. **Display wallet information**: the minimal information to display is the address of the connected account to let the users know which account they are using. A lot of dapps on Tezos also display the XTZ balance, as well as the network the dapp is connected to (Mainnet/testnet) or the wallet used for the connection. 4. **Offer the option to select the RPC node**: network traffic can get busy on Tezos, but you can provide a better UX by adding a switch for a different Tezos node if the one selected by default becomes too slow. Some power users may also like having the choice to enter the address of their favourite node! 5. **Add an option to disconnect the wallet**: some users want to switch wallets while using your dapp, so there must be a way to disconnect their wallet and connect a new one effortlessly. diff --git a/docs/developing/dev-environments.md b/docs/developing/dev-environments.md index ba0409bc0..17cbec0f8 100644 --- a/docs/developing/dev-environments.md +++ b/docs/developing/dev-environments.md @@ -44,7 +44,7 @@ See https://taqueria.io/. To test smart contracts and dApps, you can use these test environments: -- Test networks behave like Tezos mainnet but have differences that make it easier to test on them, such as faucets that provide free tokens and reduced block times for faster testing. +- Test networks behave like Tezos Mainnet but have differences that make it easier to test on them, such as faucets that provide free tokens and reduced block times for faster testing. - Sandbox environments like [Flextesa](https://tezos.gitlab.io/flextesa/) run Tezos nodes locally on your computer in a sandbox mode. For more information about test environments, see [Using sandboxes and testnets](./testnets). diff --git a/docs/developing/information/block-explorers.md b/docs/developing/information/block-explorers.md index 202b9631d..d91fee70d 100644 --- a/docs/developing/information/block-explorers.md +++ b/docs/developing/information/block-explorers.md @@ -27,7 +27,7 @@ Block explorers are not only made for casual users to check if their coins are s Block explorers are also used by: * blockchain engineers who develop and debug new features in sandboxes (e.g. new blockchain consensus). -* app developers who need debugging tools and more visibility into the current and past state of their contracts running on internal testnets and the mainnet. +* app developers who need debugging tools and more visibility into the current and past state of their contracts running on internal testnets and Mainnet. * bakers and staking services who need reliable data about delegation and earnings history to calculate correct payouts, plan their bond pools and execute operations. * less technical user groups like auditors and regulators with strict requirements for data quality, as they need to access a trusted copy of the full on-chain history in a format that's easy to digest for their spreadsheets and compliance tools. diff --git a/docs/developing/information/block-explorers/inspect-contract-tzstats.md b/docs/developing/information/block-explorers/inspect-contract-tzstats.md index 26c54622e..bef607eb4 100644 --- a/docs/developing/information/block-explorers/inspect-contract-tzstats.md +++ b/docs/developing/information/block-explorers/inspect-contract-tzstats.md @@ -236,7 +236,7 @@ All these API calls can of course be made from any libraries and thus can be aut # Conclusion -tzstats.com is extremely useful to monitor what is happening on the mainnet and public testnets. +tzstats.com is extremely useful to monitor what is happening on Mainnet and public testnets. All the pieces of information regarding the cycles, the blocks, the transactions, the smart contracts, etc... can quickly be found, thanks to a user-friendly interface. In addition, _TzStats_ provides a complete and free REST API (for non-commercial use), without any authentication or enforcement of rate limits (as long as it remains reasonable). See the introduction of the [Tzstats API](https://tzstats.com/docs/api#tezos-api). diff --git a/docs/developing/sandbox.md b/docs/developing/sandbox.md index bb68585b3..89c3e0d62 100644 --- a/docs/developing/sandbox.md +++ b/docs/developing/sandbox.md @@ -4,7 +4,7 @@ authors: 'Mathias Hiron, Nomadic Labs, Tim McMackin, TriliTech' lastUpdated: 18th October 2023 --- -Local sandboxes allow you to test your work without sending any transactions to Tezos mainnet or testnets. +Local sandboxes allow you to test your work without sending any transactions to Tezos Mainnet or testnets. The **sandboxed mode** of `octez-client` makes it possible to test your contracts or other projects while interacting with actual nodes, but without using a public test network or creating your own private network. In sandboxed mode, `octez-client` can create one or more local nodes for this. diff --git a/docs/tutorials/build-your-first-app/wallets-tokens.md b/docs/tutorials/build-your-first-app/wallets-tokens.md index 2dbf60e7c..b95d424d3 100644 --- a/docs/tutorials/build-your-first-app/wallets-tokens.md +++ b/docs/tutorials/build-your-first-app/wallets-tokens.md @@ -41,7 +41,7 @@ This is the address that applications use to work with your wallet. It may take a few minutes for the faucet to send the tokens and for those tokens to appear in your wallet. - You can use the faucet as much as you need to get tokens on the testnet, but those tokens are worthless and cannot be used on mainnet. + You can use the faucet as much as you need to get tokens on the testnet, but those tokens are worthless and cannot be used on Mainnet. ![Fund your wallet using the Ghostnet Faucet](/img/tutorials/wallet-funding.png) diff --git a/docs/tutorials/create-an-nft/nft-taquito.md b/docs/tutorials/create-an-nft/nft-taquito.md index 920354c01..296f2acc5 100644 --- a/docs/tutorials/create-an-nft/nft-taquito.md +++ b/docs/tutorials/create-an-nft/nft-taquito.md @@ -272,7 +272,7 @@ For this contract, the initial storage state is in the comment at the end of the There are many ways to originate a contract on Tezos. For a tutorial on using the command line, see [Deploy a smart contract](../smart-contract/). -Before you originate your contract to the main Tezos network (referred to as *mainnet*), you can originate it to a testnet. +Before you originate your contract to the main Tezos network (referred to as *Mainnet*), you can originate it to a testnet. Testnets are useful for testing Tezos operations because testnets provide tokens for free so you can work with Tezos without spending real tokens. This tutorial uses the online LIGO IDE at https://ide.ligolang.org/ because you don't have to install any tools to use it. @@ -364,7 +364,7 @@ If you see an error, make sure that you copied the entire contract file. 1. Open a Tezos block explorer such as [TzKT](https://tzkt.io) or [Better Call Dev](https://better-call.dev/). - 1. Set the explorer to Ghostnet instead of mainnet. + 1. Set the explorer to Ghostnet instead of Mainnet. 1. Paste the contract address into the search field and press Enter. diff --git a/docs/tutorials/create-an-nft/nft-tznft.md b/docs/tutorials/create-an-nft/nft-tznft.md index fccfd2085..b9bf87f3d 100644 --- a/docs/tutorials/create-an-nft/nft-tznft.md +++ b/docs/tutorials/create-an-nft/nft-tznft.md @@ -498,7 +498,7 @@ The command is the same as for the sandbox: 1. Go to a block explorer, such as https://tzkt.io. - 1. Set the block explorer to use testnet instead of Tezos mainnet. + 1. Set the block explorer to use testnet instead of Tezos Mainnet. 1. In the search field, paste the address of the collection and press Enter. @@ -515,7 +515,7 @@ tznft transfer --nft my_collection --signer my-account --batch 'my-account, othe ## Summary Now you can create, test, and deploy NFTs locally and to testnets. -The process for minting NFTs to Tezos mainnet is the same, but you must use an account with real XTZ in it to pay the transaction fees. +The process for minting NFTs to Tezos Mainnet is the same, but you must use an account with real XTZ in it to pay the transaction fees. -To continue your work with smart rollups, you can you can explore examples from the [kernel gallery](https://gitlab.com/tezos/kernel-gallery/-/tree/main/) or create your own. +To continue your work with Smart Rollups, you can you can explore examples from the [kernel gallery](https://gitlab.com/tezos/kernel-gallery/-/tree/main/) or create your own. ## References - [Smart rollup documentation](https://tezos.gitlab.io/alpha/smart_rollups.html) - [Smart rollup kernel SDK](https://gitlab.com/tezos/tezos/-/tree/master/src/kernel_sdk) - [Smart rollup kernel examples](https://gitlab.com/tezos/kernel-gallery/-/tree/main/) -- [Tezos smart rollups resources](https://airtable.com/shrvwpb63rhHMiDg9/tbl2GNV1AZL4dkGgq) +- [Tezos Smart Rollups resources](https://airtable.com/shrvwpb63rhHMiDg9/tbl2GNV1AZL4dkGgq) - [Tezos testnets](https://teztnets.xyz/) - [Originating the installer kernel](https://tezos.stackexchange.com/questions/4784/how-to-originating-a-smart-rollup-with-an-installer-kernel/5794#5794) - [Docker documentation](https://docs.docker.com/get-started/) From b41b36ed31432eb9f15386031a6cf7b0519b2f95 Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Tue, 7 Nov 2023 15:40:17 -0500 Subject: [PATCH 4/4] Capitalize Dailynet --- docs/architecture/smart-rollups.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/architecture/smart-rollups.md b/docs/architecture/smart-rollups.md index c9ac397e4..044a4c918 100644 --- a/docs/architecture/smart-rollups.md +++ b/docs/architecture/smart-rollups.md @@ -528,7 +528,7 @@ EMESSAGE=$(octez-smart-rollup-client-Pt${CURRENT_PROTOCOL} encode outbox message ## Triggering Execution of an Outbox Message Once an outbox message has been pushed to the outbox by the kernel at -some level `${L}`, the user needs to wait for the commitment that includes this level to be cemented. On dailynet, the cementation process +some level `${L}`, the user needs to wait for the commitment that includes this level to be cemented. On Dailynet, the cementation process of a non-disputed commitment is 40 blocks long while on Mainnet, it is 2 weeks long.