docs(interrealm): fix small typos (#4236)

Author: aeddi

docs/resources/gno-interrealm.md

@@ -1,6 +1,6 @@
 # Interrealm Specification
 
-Gno extends Go's type system with a interrealm rules.  These rules can be
+Gno extends Go's type system with interrealm rules. These rules can be
 checked during the static type-checking phase (but at the moment they are
 partially dependent on runtime checks).
 
@@ -24,7 +24,7 @@ A function declared in a realm package when called:
 
 The `crossing()` statement must be the first statement of a function's body.
 It is illegal to use anywhere else, and cannot be used in p packages. Functions
-that begin with the `crossing()` statement are called "crossing" functions".
+that begin with the `crossing()` statement are called "crossing functions".
 
 A crossing function declared in a realm different than the last explicitly
 crossed realm *must* be called like `cross(fn)(...)`. That is, functions of
@@ -54,7 +54,7 @@ else's pen it is still your signature; signature:pen :: current:borrowed.
 A crossing method declared in a realm cannot modify the receiver if the object
 resides in a different realm. However not all methods are required to be
 crossing methods, and crossing methods may still read the state of the
-receiver (and in general anything reacheable is readible).
+receiver (and in general anything reachable is readable).
 
 New unreal objects reachable from the borrowed realm (or current realm if there
 was no method call that borrowed) become persisted in the borrowed realm (or
@@ -68,7 +68,7 @@ MsgCall can only call (realm) crossing functions.
 MsgRun will run a file's `main()` function in the user's realm and may call 
 both crossing functions and non-crossing functions.
 
-A realm package's initialization (including init() calls) execute with current
+A realm package's initialization (including `init()` calls) execute with current
 realm of itself, and it `std.PreviousRealm()` will panic unless the call stack
 includes a crossing function called like `cross(fn)(...)`.
 
@@ -100,7 +100,7 @@ implicit and generally not obvious without more language features.
 
 Code declared in p packages (or declared in "immutable" realm packages) can
 help different realms enforce contracts trustlessly, even those that involve
-the caller's current realm. Otherwise two mutable (upgreadeable) realms cannot
+the caller's current realm. Otherwise two mutable (upgradeable) realms cannot
 export trust unto the chain because functions declared in those two realms can
 be upgraded.
 
@@ -109,19 +109,19 @@ future Gno versions.
 
 ### Usage
 
-P package code cannot containing crossing functions, nor use crossing().  P
+P package code cannot contain crossing functions, nor use `crossing()`. P
 package code also cannot import R realm packages. But code can call named
 crossing functions e.g. those passed in as parameters.
 
-You must declare a public realm function to be crossing() if it is intended to
+You must declare a public realm function to be `crossing()` if it is intended to
 be called by end users, because users cannot MsgCall non-crossing functions
 (for safety/consistency) or p package functions (there's no point).
 
 Utility functions that are a common sequence of non-crossing logic can be
 offered in realm packages as non-crossing functions. These can also import and
 use other realm utility non-crossing functions; whereas p packages cannot
 import realm packages at all. And convenience/utility functions that are being
-staged before publishing as permanent p code should also reside in upgreadeable
+staged before publishing as permanent p code should also reside in upgradeable
 realms.
 
 Generally you want your methods to be non-crossing. Because they should work
@@ -141,7 +141,7 @@ overrides for testing are defined in `testing/stdlibs/std/std.gno/go`. All
 stdlibs functions are available unless overridden by the latter.
 
 `std.CurrentRealm()` shifts to `std.PreviousRealm()` if and only if a function
-is called like cross(fn)(...).
+is called like `cross(fn)(...)`.
 
 #### MsgCall
 
@@ -212,7 +212,7 @@ func main() {
 }
 ```
 
-Notice in gnovm/pkg/gnolang/misc.go, the following:
+Notice in `gnovm/pkg/gnolang/misc.go`, the following:
 
 ```go
 // For keeping record of package & realm coins.
@@ -241,7 +241,7 @@ func DerivePkgBech32Addr(pkgPath string) crypto.Bech32Address {
 ```
 
 These function names are distinct from what is available in Gno
-from stdlibs/std/crypto.gno:
+from `stdlibs/std/crypto.gno`:
 
 ```go
 // Returns a crypto hash derived pkgPath, unless pkgPath is a MsgRun run path,
@@ -255,14 +255,14 @@ func DerivePkgAddr(pkgPath string) Address {
 1. `std.DerivePkgAddr("gno.land/r/name123/realm")` - bech32 from hash(path)
 2. `std.DerivePkgAddr("gno.land/r/g1user/run")` - bech32 substring "g1user"
 
-Therefore in the MsgRun file's init() function the previous realm and current
+Therefore in the MsgRun file's `init()` function the previous realm and current
 realm have different pkgpaths (the origin caller always has empty pkgpath) but
 the address is the same.
 
 #### MsgAddPackage
 
 During MsgAddPackage `std.PreviousRealm()` refers to the package deployer both
-in gloval var decls as well as inside `init()` functions. After that the
+in global var decls as well as inside `init()` functions. After that the
 package deployer is no longer provided, so packages need to remember the
 deployer in the initialization if needed.
 
@@ -320,9 +320,9 @@ The `gnovm/tests/stdlibs/testing/context_testing.gno` file provides functions
 for overriding frame details from Gno test code.
 
 `testing.SetRealm(std.NewUserRealm("g1user"))` is identical to
-`testing.SetOriginCaller("g1user"). Both will override the Gno frame to make it
+`testing.SetOriginCaller("g1user")`. Both will override the Gno frame to make it
 appear as if the current frame is the end user signing with a hardware signer.
-Both will also set ExecContext.OriginCaller to that user. One of these will
+Both will also set `ExecContext.OriginCaller` to that user. One of these will
 become deprecated.
 
 #### Gno test cases with `_test.gno` like `TestFoo(t *testing.T)`
@@ -421,9 +421,9 @@ func main() {
 
 #### Future Work
 
-std.SetOriginCaller() should maybe be deprecated in favor of
-std.SetRealm(std.NewUserRealm(user)) renamed to
-std.SetRealm(std.NewOriginRealm(user)).
+`std.SetOriginCaller()` should maybe be deprecated in favor of
+`std.SetRealm(std.NewUserRealm(user))` renamed to
+`std.SetRealm(std.NewOriginRealm(user))`.
 
-std.SetRealm(std.NewCodeRealm(path)) renamed to
-std.SetRealm(std.NewPackageRealm(path)).
+`std.SetRealm(std.NewCodeRealm(path))` renamed to
+`std.SetRealm(std.NewPackageRealm(path))`.