Merge branch 'master' into feat/gnodev-load-txs

gnolang · Jun 6, 2024 · 24dd185 · 24dd185
2 parents 2650a25 + 7bced19
commit 24dd185
Show file tree

Hide file tree

Showing 13 changed files with 42 additions and 433 deletions.
diff --git a/.benchmarks/README.md b/.benchmarks/README.md
@@ -19,7 +19,7 @@ Things to take into account:
 - All benchmarks on a package will be shown on the same graph.
 - The value on `package` and `benchmarks` are regular expressions.
 - You have to explicitly add your new package here to make it appears on generated graphs.
-- If you have benchmarks on the same package that takes much more time pero op than the rest, you should divide it into a separate graph for visibility. In this example we can see how we separated tests from the gnolang package into the ones finishing with `Equality` and `LoopyMain`, because `LoopyMain` is taking an order of magnitude more time per operation than the other tests:
+- If you have benchmarks on the same package that takes much more time per op than the rest, you should divide it into a separate graph for visibility. In this example we can see how we separated tests from the gnolang package into the ones finishing with `Equality` and `LoopyMain`, because `LoopyMain` is taking an order of magnitude more time per operation than the other tests:
 ```yaml
       - name: Equality benchmarks (gnovm)
         benchmarks: [ '.Equality' ]
@@ -31,4 +31,4 @@ Things to take into account:
 
 ## Add new checks for PRs
 
-If we want to add a new package to check all the fast benchmarks on it on every PR, we should have a look into [gobenchdata-checks.yml](./gobenchdata-checks.yml).
+If we want to add a new package to check all the fast benchmarks on it on every PR, we should have a look into [gobenchdata-checks.yml](./gobenchdata-checks.yml).
diff --git a/docs/assets/how-to-guides/creating-grc721/mynonfungibletoken-1.gno b/docs/assets/how-to-guides/creating-grc721/mynonfungibletoken-1.gno
diff --git a/docs/assets/how-to-guides/creating-grc721/mynonfungibletoken-2.gno b/docs/assets/how-to-guides/creating-grc721/mynonfungibletoken-2.gno
diff --git a/docs/concepts/effective-gno.md b/docs/concepts/effective-gno.md
@@ -723,7 +723,7 @@ See also: https://github.com/gnolang/gno/tree/master/examples/gno.land/r/demo/wu
 
 <!-- TODO:
 
-- packages and realms versionning
+- packages and realms versioning
 - code generation
 - unit tests, fuzzing tests, example tests, txtar
 - shipping non-contract stuff with the realm: client, documentation, assets

diff --git a/docs/concepts/packages.md b/docs/concepts/packages.md
@@ -41,12 +41,12 @@ The role of each function is as follows:
 
 Two types of contracts exist in`grc20`:
 
-1. `AdminToken`\
-   \- Implements the token factory with `Helper` functions.\
-   \- The underlying struct should not be exposed to users. However, it can be typecasted as UserToken using the `GRC20()` method.
-2. `UserToken`\
-   \- Implements the `IGRC20` interface.\
-   \- The underlying struct can be exposed to users. Created with the `GRC20()` method of `adminToken`.
+1. `AdminToken`
+   - Implements the token factory with `Helper` functions.
+   - The underlying struct should not be exposed to users. However, it can be typecasted as UserToken using the `GRC20()` method.
+2. `UserToken`
+   - Implements the `IGRC20` interface.
+   - The underlying struct can be exposed to users. Created with the `GRC20()` method of `adminToken`.
 
 ## `grc721`