Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix typos in documentation files #20817

Merged
merged 2 commits into from
Jan 8, 2025
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/content/guides/developer/coin/loyalty.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ The loyalty.move source file contains the `examples::loyalty` module code that c

{@inject: examples/move/token/sources/loyalty.move#struct=loyalty noComments}

The `init` function of the module uses the `LOYALTY` OTW to create the token. All `init` functions run one time only at the package publish event. The initializer function makes use of the OTW `LOYALTY` type defined previously in its call to `create_currency`. The function also defines a policy, sending both the policy capability and trasury capability to the address associated with the publish event. The holder of these transferrable capabilities can mint new `LOYALTY` tokens and modify their policies.
The `init` function of the module uses the `LOYALTY` OTW to create the token. All `init` functions run one time only at the package publish event. The initializer function makes use of the OTW `LOYALTY` type defined previously in its call to `create_currency`. The function also defines a policy, sending both the policy capability and treasury capability to the address associated with the publish event. The holder of these transferrable capabilities can mint new `LOYALTY` tokens and modify their policies.

{@inject: examples/move/token/sources/loyalty.move#fun=init noComments}

Expand Down
2 changes: 1 addition & 1 deletion docs/content/guides/developer/cryptography/groth16.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ The following example demonstrates how to create a Groth16 proof from a statemen

### Create circuit

In this example, we crate a proof which demonstrates that we know a factorisation `a * b = c` of a publicly known number `c` without revealing `a` and `b`.
In this example, we create a proof which demonstrates that we know a factorisation `a * b = c` of a publicly known number `c` without revealing `a` and `b`.

```circom
pragma circom 2.1.5;
Expand Down
2 changes: 1 addition & 1 deletion docs/content/guides/developer/cryptography/multisig.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -230,7 +230,7 @@ Each successful call to the command receives a response similar to the following
╰──────────────┴─────────────────────────────╯
```

Create two more shell variables to store the signatures, replaceing `<SIGNATURE-HASH-*>` with the values from the previous command responses.
Create two more shell variables to store the signatures, replacing `<SIGNATURE-HASH-*>` with the values from the previous command responses.

```sh
$ SIG_1=<SIGNATURE-HASH-ED25519>
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -353,7 +353,7 @@ You might want to cache the ephemeral key pair along with the ZKP for future use

However, the ephemeral key pair needs to be treated as a secret akin to a key pair in a traditional wallet. This is because if both the ephemeral private key and ZK proof are revealed to an attacker, then they can typically sign any transaction on behalf of the user (using the same process described previously).

Consequently, you should not store them persistently in an unsecure storage location, on any platform. For example, on browsers, use session storage instead of local storage to store the ephemeral key pair and the ZK proof. This is because session storage automatically clears its data when the browser session ends, while data in local storage persists indefinitely.
Consequently, you should not store them persistently in an insecure storage location, on any platform. For example, on browsers, use session storage instead of local storage to store the ephemeral key pair and the ZK proof. This is because session storage automatically clears its data when the browser session ends, while data in local storage persists indefinitely.
ronny-mysten marked this conversation as resolved.
Show resolved Hide resolved

## Efficiency considerations

Expand Down
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: Querying Sui RPC with GraphQL
description: Intoductory guide to making queries of the Sui RPC using the GraphQL service.
description: Introductory guide to making queries of the Sui RPC using the GraphQL service.
---

The quickest way to access the GraphQL service for Sui RPC is through the online IDE that provides a complete toolbox for fetching data and executing transactions on the network. The online IDE provides features such as auto-completion (use Ctrl+Space or just start typing), built-in documentation (Book icon, top-left), multi-tabs, and more.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -421,7 +421,7 @@ With Sui installed, you can interact with Sui networks using the Sui CLI. For mo
## Installing Sui developer tools

If you use VSCode, you can install the [Move extension](https://marketplace.visualstudio.com/items?itemName=mysten.move) to get language server support for Move, as well as support for building, testing, and debugging Move code within the IDE.
You can install the extension either by searhing the fully-qualified extension name, `Mysten.move`, in the extension view, or by pressing `Ctrl-P` or `Cmd-P` and typing `ext install mysten.move`.
You can install the extension either by searching the fully-qualified extension name, `Mysten.move`, in the extension view, or by pressing `Ctrl-P` or `Cmd-P` and typing `ext install mysten.move`.
Installing the Move extension also installs the appropriate `move-analyzer` binary for your operating system, as well as the [Move Trace Debugger](https://marketplace.visualstudio.com/items?itemName=mysten.move-trace-debug) extension, and [Move Syntax](https://marketplace.visualstudio.com/items?itemName=damirka.move-syntax) extension.

There are also community Move packages for [Emacs](https://github.com/amnn/move-mode) and [Vim](https://github.com/yanganto/move.vim).
Expand Down
Loading