docs: Gno.land to gno.land (#2514)

Update `Gno.land` to `gno.land`, in order for the documentation to conform to the proper lowercase usage --------- Co-authored-by: Milos Zivkovic <[email protected]>
gnolang · Jul 8, 2024 · 8ddf0d8 · 8ddf0d8
1 parent aec02dc
commit 8ddf0d8
Show file tree

Hide file tree

Showing 45 changed files with 131 additions and 130 deletions.
diff --git a/.gitpod.yml b/.gitpod.yml
@@ -31,7 +31,7 @@ tasks:
 
 ports:
   - name: gnoweb
-    description: "the Gno.land web server"
+    description: "the gno.land web server"
     port: 8888
     onOpen: open-preview
 

diff --git a/README.md b/README.md
@@ -10,7 +10,7 @@
 
 Gno is an interpreted and fully-deterministic implementation of the Go
 programming language, designed to build succinct and composable smart contracts.
-The first blockchain to use it is Gno.land, a
+The first blockchain to use it is gno.land, a
 [Proof of Contribution](./docs/concepts/proof-of-contribution.md)-based chain, backed by
 a variation of the [Tendermint](https://docs.tendermint.com/v0.34/introduction/what-is-tendermint.html)
 consensus engine.
@@ -47,7 +47,7 @@ repository offers more resources to dig into. We are eager to see your first PR!
 </a>
 </br></br>
 
-[Gno Playground](https://play.gno.land), available at [play.gno.land](https://play.gno.land), is a web app that allows users to write, share, and deploy Gno code. Developers can seamlessly test, debug, and deploy realms and packages on Gno.land, while being able to collaborate with peers to work on projects together and seek assistance. A key feature of Gno Playground is the ability to get started without the need to install any tools or manage any services, offering immediate access and convenience for users.
+[Gno Playground](https://play.gno.land), available at [play.gno.land](https://play.gno.land), is a web app that allows users to write, share, and deploy Gno code. Developers can seamlessly test, debug, and deploy realms and packages on gno.land, while being able to collaborate with peers to work on projects together and seek assistance. A key feature of Gno Playground is the ability to get started without the need to install any tools or manage any services, offering immediate access and convenience for users.
 
 ## Repository structure
 

diff --git a/contribs/gnofaucet/serve.go b/contribs/gnofaucet/serve.go
@@ -154,7 +154,7 @@ func execServe(ctx context.Context, cfg *serveCfg, io commands.IO) error {
 	// Parse static gas values.
 	// It is worth noting that this is temporary,
 	// and will be removed once gas estimation is enabled
-	// on Gno.land
+	// on gno.land
 	gasFee := std.MustParseCoin(defaultGasFee)
 
 	gasWanted, err := strconv.ParseInt(defaultGasWanted, 10, 64)

diff --git a/docs/concepts/concepts.md b/docs/concepts/concepts.md
@@ -5,4 +5,4 @@ id: concepts
 # Concepts
 
 Welcome to the **Concepts** section for Gno. This section outlines the most important
-concepts related to Gno & Gno.land.
+concepts related to Gno & gno.land.
diff --git a/docs/concepts/gno-language.md b/docs/concepts/gno-language.md
@@ -21,8 +21,8 @@ serialize and deserialize objects to persist them into a database (unlike progra
 
 ## How Gno Differs from Go
 
-The composable nature of Go/Gno allows for type-checked interactions between contracts, making Gno.land safer and more
-powerful, as well as operationally cheaper and faster. Smart contracts on Gno.land are light, simple, more focused, and
+The composable nature of Go/Gno allows for type-checked interactions between contracts, making gno.land safer and more
+powerful, as well as operationally cheaper and faster. Smart contracts on gno.land are light, simple, more focused, and
 easily interoperable - they represent a network of interconnected contracts rather than siloed monoliths that limit
 interactions with other contracts.
 

diff --git a/docs/concepts/gno-modules.md b/docs/concepts/gno-modules.md
@@ -4,7 +4,7 @@ id: gno-modules
 
 # Gno Modules
 
-The packages and realms containing `gno.mod` file can be referred as Gno modules. `gno.mod` file is introduced to enhance local testing and handle dependency management while testing Gno packages/realms locally. At the time of writing, `gno.mod` is only used by the `gno` tool for local development, and it is disregarded on the Gno.land chain.
+The packages and realms containing `gno.mod` file can be referred as Gno modules. `gno.mod` file is introduced to enhance local testing and handle dependency management while testing Gno packages/realms locally. At the time of writing, `gno.mod` is only used by the `gno` tool for local development, and it is disregarded on the gno.land chain.
 
 ## What is the gno.mod file for?
 

diff --git a/docs/concepts/portal-loop.md b/docs/concepts/portal-loop.md
@@ -5,7 +5,7 @@ id: portal-loop
 # Portal Loop
 
 Portal Loop is an always-up-to-date staging testnet that allows for using
-the latest version of Gno, Gno.land, and TM2. By utilizing the power of Docker
+the latest version of Gno, gno.land, and TM2. By utilizing the power of Docker
 & the [tx-archive](https://github.com/gnolang/tx-archive) tool, the Portal Loop can run the latest code from the 
 master branch on the [Gno monorepo](https://github.com/gnolang/gno), 
 while preserving most/all of the previous transaction data. 

diff --git a/docs/concepts/stdlibs/events.md b/docs/concepts/stdlibs/events.md
@@ -9,7 +9,7 @@ id: events
 Events in Gno are a fundamental aspect of interacting with and monitoring
 on-chain applications. They serve as a bridge between the on-chain environment 
 and off-chain services, making it simpler for developers, analytics tools, and 
-monitoring services to track and respond to activities happening in Gno.land.
+monitoring services to track and respond to activities happening in gno.land.
 
 Gno events are pieces of data that log specific activities or changes occurring 
 within the state of an on-chain app. These activities are user-defined; they might

diff --git a/docs/concepts/tendermint2.md b/docs/concepts/tendermint2.md
@@ -6,7 +6,7 @@ id: tendermint2
 
 **Disclaimer: Tendermint2 is currently part of the Gno monorepo for streamlined development.**
 
-**Once Gno.land is on the mainnet, Tendermint2 will operate independently, including for governance,
+**Once gno.land is on the mainnet, Tendermint2 will operate independently, including for governance,
 on https://github.com/tendermint/tendermint2.**
 
 ## Problems

diff --git a/docs/concepts/testnets.md b/docs/concepts/testnets.md
@@ -4,7 +4,7 @@ id: testnets
 
 # Gno Testnets
 
-This page documents all Gno.land testnets, what their properties are, and how
+This page documents all gno.land testnets, what their properties are, and how
 they are meant to be used. For testnet configuration, visit the 
 [reference section](../reference/network-config.md).
 
@@ -93,7 +93,7 @@ of Gno, and it can contain new on-chain code
   - There is no versioning strategy for test3. It will stay the way it is, until
 the team chooses to shut it down.
 
-Since Gno.land is designed with open-source in mind, anyone can see currently 
+Since gno.land is designed with open-source in mind, anyone can see currently 
 available code by browsing the [test3 homepage](https://test3.gno.land/). 
 
 Test3 is a single-node testnet, ran by the Gno core team. There is no plan to 

diff --git a/docs/getting-started/local-setup/browsing-gnoland.md b/docs/getting-started/local-setup/browsing-gnoland.md
@@ -2,11 +2,11 @@
 id: browsing-gnoland
 ---
 
-# Browsing Gno.land
+# Browsing gno.land
 
 ## Overview
 In this tutorial, you will learn how to browse [realms](../../concepts/realms.md)
-and [packages](../../concepts/packages.md) deployed to a Gno.land chain. 
+and [packages](../../concepts/packages.md) deployed to a gno.land chain. 
 You will understand how the `Render` method is utilized to achieve realm state
 visibility, and you will learn how to easily access realm APIs.
 
@@ -33,10 +33,10 @@ gno.land home page:
 
 ![homepage](../../assets/getting-started/local-setup/browsing-gno-source-code/gnoland-homepage.png)
 
-## 2. Browsing Gno.land
+## 2. Browsing gno.land
 
 ### Package source code
-Packages in Gno.land usually have names resembling `gno.land/p/<name>`. Since 
+Packages in gno.land usually have names resembling `gno.land/p/<name>`. Since 
 packages do not contain state, only their source code can be viewed on-chain. To
 learn more about packages, check out the [Packages](../../concepts/packages.md) 
 concept page.
@@ -55,7 +55,7 @@ From here, we can open any source code file of the deployed on-chain package
 and inspect its API.
 
 ### Realm source code & state
-In contrast to Packages, Realms in Gno.land usually have names resembling
+In contrast to Packages, Realms in gno.land usually have names resembling
 `gno.land/r/<name>`.
 
 Realms _do_ contain state, and in addition to being able to view their source 

diff --git a/docs/getting-started/local-setup/installation.md b/docs/getting-started/local-setup/installation.md
@@ -23,7 +23,7 @@ export PATH=$GOPATH/bin:$PATH
 ```
 
 ## 1. Cloning the repository
-To get started with a local Gno.land development environment, you must clone the
+To get started with a local gno.land development environment, you must clone the
 GitHub repository somewhere on disk:
 
 ```bash
@@ -85,8 +85,8 @@ You should get the following output:
 
 ### `gnokey`
 
-`gnokey` is the Gno.land keypair management CLI tool. It allows you to create
-keypairs, sign transactions, and broadcast them to Gno.land chains. Read more
+`gnokey` is the gno.land keypair management CLI tool. It allows you to create
+keypairs, sign transactions, and broadcast them to gno.land chains. Read more
 about `gnokey` [here](../../gno-tooling/cli/gnokey.md).
 
 To verify that the `gnokey` binary is installed system-wide, you can run:

diff --git a/docs/getting-started/local-setup/interacting-with-gnoland.md b/docs/getting-started/local-setup/interacting-with-gnoland.md
@@ -2,10 +2,10 @@
 id: interacting-with-gnoland
 ---
 
-# Interacting with Gno.land code
+# Interacting with gno.land code
 
 ## Overview
-In this tutorial, you will learn how to interact with Gno.land code.
+In this tutorial, you will learn how to interact with gno.land code.
 You will understand how to use your keypair to send transactions to realms
 and packages, send native coins, and more.
 
@@ -16,7 +16,7 @@ and packages, send native coins, and more.
 [Working with Key Pairs](working-with-key-pairs.md#adding-a-private-key-using-a-mnemonic) guide for steps
 
 ## 1. Get testnet GNOTs
-For interacting with any Gno.land chain, you will need a certain amount of GNOTs
+For interacting with any gno.land chain, you will need a certain amount of GNOTs
 to pay gas fees with. 
 
 For this example, we will use the [Portal Loop](../../concepts/testnets.md#portal-loop) 

diff --git a/docs/getting-started/local-setup/local-setup.md b/docs/getting-started/local-setup/local-setup.md
@@ -3,6 +3,7 @@ id: local-setup
 ---
 
 # Local setup
+
 This section will show you how to set up a local environment for Gno development.
-It includes instructions for installation, setting up a Gno.land keypair, 
+It includes instructions for installation, setting up a gno.land keypair,
 browsing Gno source code, and more. 
diff --git a/docs/getting-started/local-setup/working-with-key-pairs.md b/docs/getting-started/local-setup/working-with-key-pairs.md
@@ -6,7 +6,7 @@ id: working-with-key-pairs
 
 ## Overview
 In this tutorial, you will learn how to manage private user keys, which are
-required for interacting with the Gno.land blockchain. You will understand what
+required for interacting with the gno.land blockchain. You will understand what
 mnemonics are, how they are used, and how you can make interaction seamless with
 Gno.
 
@@ -83,7 +83,7 @@ The key response consists of a few pieces of information:
 - The derived address (`addr`)
 - The public key (`pub`)
 
-Using these pieces of information, we can interact with Gno.land tools and write 
+Using these pieces of information, we can interact with gno.land tools and write 
 blockchain applications.
 
 ## Generating a BIP39 mnemonic

diff --git a/docs/getting-started/playground-start.md b/docs/getting-started/playground-start.md
@@ -9,12 +9,12 @@ id: playground-start
 The Gno Playground is an innovative web-based editor and sandbox that enables developers to 
 interactively work with the Gno language. It makes coding, testing,
 and deploying simple with its diverse set of tools and features. Users can
-share code, run tests, and deploy projects to Gno.land networks, 
+share code, run tests, and deploy projects to gno.land networks, 
 making it the perfect tool to get started with Gno development.
 
 ## Prerequisites
 
-- **A Gno.land compatible wallet**
+- **A gno.land compatible wallet**
   - Currently, [Adena](https://www.adena.app/) is the preferred wallet for
 Gno.land, with more wallets being introduced in the future.
 
@@ -27,7 +27,7 @@ simple `package.gno` file:
 
 The Playground has the following features:
 - `Share` - Generate a unique, short, and shareable identifier for your Gno code.
-- `Deploy` - Connect your wallet and publish your code on Gno.land.
+- `Deploy` - Connect your wallet and publish your code on gno.land.
 - `Format` - Automatically adjust your Gno code's structure and style for optimal readability and consistency.
 - `Run` - Execute a particular expression within your code to validate its functionality and output.
 - `Test` - Execute predefined tests to verify your code's integrity and ensure it meets expected outcomes.
@@ -45,7 +45,7 @@ ensuring the shared code remains accessible over an extended period.
 ### Deploy
 
 The **Deploy** feature allows users to seamlessly deploy their Gno code to the 
-chain. After connecting a Gno.land wallet, users can select their desired 
+chain. After connecting a gno.land wallet, users can select their desired 
 package path and network for deployment.
 
 ![default_deploy](../assets/getting-started/playground/default_deploy.png)
@@ -92,10 +92,10 @@ will show you the output of the test. Read more about how Gno tests work
 The **REPL** feature allows you to experiment with the GnoVM.
 It provides a command-line interface for hands-on learning, iterative testing, and swift prototyping.
 
-## Learning about Gno.land & writing Gno code
+## Learning about gno.land & writing Gno code
 
 If you're new here, don't worry—content is regularly produced to breakdown
-Gno.land to explain its features. Dive into the essentials of Gno.land by 
+Gno.land to explain its features. Dive into the essentials of gno.land by 
 exploring the [Concepts](../concepts/concepts.md) section.
 
 To get started writing Gno code, check out the

diff --git a/docs/gno-infrastructure/premining-balances.md b/docs/gno-infrastructure/premining-balances.md
@@ -6,7 +6,7 @@ id: premining-balances
 
 ## Overview
 
-In this tutorial, you will gain an understanding on how to premine native currency on a local Gno.land chain.
+In this tutorial, you will gain an understanding on how to premine native currency on a local gno.land chain.
 Additionally, you will understand how to query the account balance after you premine it.
 
 Premining balance is the process of making sure some accounts (addresses) have specific funds when the chain initially

diff --git a/docs/gno-infrastructure/validators/connect-to-existing-chain.md b/docs/gno-infrastructure/validators/connect-to-existing-chain.md
@@ -18,7 +18,7 @@ In this tutorial, you will learn how to start a local Gno node and connect to an
 
 ## 1. Initialize the node directory
 
-To initialize a new Gno.land node working directory (configuration and secrets), make sure to
+To initialize a new gno.land node working directory (configuration and secrets), make sure to
 follow [Step 1](./setting-up-a-new-chain.md#1-generate-the-node-directory-secrets--config) from the
 chain setup tutorial.
 
@@ -97,7 +97,7 @@ gnoland config set p2p.seeds "[email protected]:2
 
 ## 6. Start the node
 
-Now that we've set up the local node configuration, and added peering info, we can start the Gno.land node:
+Now that we've set up the local node configuration, and added peering info, we can start the gno.land node:
 
 ```shell
 gnoland start \

diff --git a/docs/gno-infrastructure/validators/faq.md b/docs/gno-infrastructure/validators/faq.md
@@ -6,44 +6,44 @@ id: validators-faq
 
 ## General Concepts
 
-### What is a Gno.land validator?
+### What is a gno.land validator?
 
 Gno.land is based on [Tendermint2](https://docs.gno.land/concepts/tendermint2) that relies on a set of validators
 selected based on [Proof of Contribution](https://docs.gno.land/concepts/proof-of-contribution) (PoC) to secure the
 network. Validators are tasked with participating in consensus by committing new blocks and broadcasting votes.
-Validators are compensated with a portion of transaction fees generated in the network. In Gno.land, the voting power of
+Validators are compensated with a portion of transaction fees generated in the network. In gno.land, the voting power of
 all validators are equally weighted to achieve a high nakamoto coefficient and fairness.
 
 ### What is Tendermint2?
 
-[Tendermint2](https://docs.gno.land/concepts/tendermint2) (TM2) is the consensus protocol that powers Gno.land. TM2 is a
+[Tendermint2](https://docs.gno.land/concepts/tendermint2) (TM2) is the consensus protocol that powers gno.land. TM2 is a
 successor of [Tendermint Core](https://github.com/tendermint/tendermint2), a de facto consensus framework for building
 Proof of Stake blockchains. The design philosophy of TM2 is to create “complete software” without any vulnerabilities
 with development focused on minimalism, dependency removal, and modularity.
 
 ### What is Proof of Contribution?
 
 [Proof of Contribution](https://docs.gno.land/concepts/proof-of-contribution) (PoC) is a novel consensus mechanism that
-secures Gno.land. PoC weighs expertise and alignment with the project to evaluate the contribution of individuals or
+secures gno.land. PoC weighs expertise and alignment with the project to evaluate the contribution of individuals or
 teams who govern and operate the chain. Unlike Proof of Stake (PoS), validators are selected via governance of
 Contributors based on their reputation and technical proficiency. The voting power of the network is equally distributed
 across all validators for higher decentralization. A portion of all transaction fees paid to the network are evenly
 shared between all validators to provide a fair incentive structure.
 
-### How does Gno.land differ from the Cosmos Hub?
+### How does gno.land differ from the Cosmos Hub?
 
 In Cosmos Hub, validators are selected based on the amount of staked `ATOM` tokens delegated. This means that anyone
 with enough capital can join as a validator only to seek economic incentives without any alignment or technical
 expertise. This system leads to an undesirable incentive structure in which validators are rewarded purely based on the
 capital delegated, regardless of the quality of their infrastructure or service.
 
-On the contrary, validators in Gno.land must be reviewed and verified to have made significant contributions in order to
+On the contrary, validators in gno.land must be reviewed and verified to have made significant contributions in order to
 join the validator set. This property resembles the validator selection mechanism
 in [Proof of Authority](https://openethereum.github.io/Proof-of-Authority-Chains). Furthermore, all validators are
 evenly rewarded to ensure that the entire validator set is fairly incentivized to ensure the sustainability of the
 network.
 
-### What stage is the Gno.land project in?
+### What stage is the gno.land project in?
 
 Gno.land is currently in Testnet 3, the single-node testnet stage. The next version, Testnet 4, is scheduled to go live
 in Q3 2024, which will include a validator set implementation for a multinode environment.
@@ -62,7 +62,7 @@ testnets, visit [Gno Testnets](https://docs.gno.land/concepts/testnets).
 
 ### What are the incentives for running a validator?
 
-Network transaction fees paid on the Gno.land in `GNOT` are collected, from which a portion is directed to reward
+Network transaction fees paid on the gno.land in `GNOT` are collected, from which a portion is directed to reward
 validators for their work. All validators fairly receive an equal amount of rewards.
 
 ### How many validators will there be in mainnet?

diff --git a/docs/gno-infrastructure/validators/overview.md b/docs/gno-infrastructure/validators/overview.md
@@ -44,12 +44,12 @@ will be determined following thorough testing and optimization experiments in Te
 
 ## Good Validators
 
-Validators for Gno.land are trusted to demonstrate professionalism and responsibility. Below are best practices that can
+Validators for gno.land are trusted to demonstrate professionalism and responsibility. Below are best practices that can
 be expected from a good, reliable validator.
 
 #### Ecosystem Contribution
 
-- Contributing to the core development of the Gno.land project
+- Contributing to the core development of the gno.land project
 - Providing useful tools or infrastructure services (wallets, explorers, public RPCs, etc.)
 - Creating educational materials to guide new members
 - Localizing documentation or content to lower language or cultural barriers
@@ -75,7 +75,7 @@ be expected from a good, reliable validator.
 
 ## Community
 
-Join the official Gno.land community in various channels to receive the latest updates about the project and actively
+Join the official gno.land community in various channels to receive the latest updates about the project and actively
 communicate with other validators and contributors.
 
 - [Gno.land Blog](https://gno.land/r/gnoland/blog)
@@ -84,7 +84,7 @@ communicate with other validators and contributors.
 
 :::info
 
-The validator set implementation in Gno.land is abstracted away from the consensus mechanism inside the `r/sys/vals`
+The validator set implementation in gno.land is abstracted away from the consensus mechanism inside the `r/sys/vals`
 realm. The realm is not production ready yet, and is still under active development. Proposals and contributions to
 improve and complete the implementation are welcome.