chore: remove duplication words (#20754)

crates/sui-framework/docs/sui-framework/coin.md

@@ -883,7 +883,7 @@ allows for specific addresses to have their coins frozen. When an address is add
 deny list, it is immediately unable to interact with the currency's coin as input objects.
 Additionally at the start of the next epoch, they will be unable to receive the currency's
 coin.
-The <code>allow_global_pause</code> flag enables an additional API that will cause all addresses to be
+The <code>allow_global_pause</code> flag enables an additional API that will cause all addresses to
 be denied. Note however, that this doesn't affect per-address entries of the deny list and
 will not change the result of the "contains" APIs.
 

crates/sui-framework/packages/sui-framework/sources/coin.move

@@ -241,7 +241,7 @@ public fun create_currency<T: drop>(
 /// deny list, it is immediately unable to interact with the currency's coin as input objects.
 /// Additionally at the start of the next epoch, they will be unable to receive the currency's
 /// coin.
-/// The `allow_global_pause` flag enables an additional API that will cause all addresses to be
+/// The `allow_global_pause` flag enables an additional API that will cause all addresses to
 /// be denied. Note however, that this doesn't affect per-address entries of the deny list and
 /// will not change the result of the "contains" APIs.
 public fun create_regulated_currency_v2<T: drop>(

crates/sui/src/keytool.rs

@@ -191,7 +191,7 @@ pub enum KeyToolCommand {
     /// [enum SuiKeyPair] (Base64 encoded of 33-byte `flag || privkey`) or `type AuthorityKeyPair`
     /// (Base64 encoded `privkey`). It prints its Base64 encoded public key and the key scheme flag.
     Show { file: PathBuf },
-    /// Create signature using the private key for for the given address (or its alias) in sui keystore.
+    /// Create signature using the private key for the given address (or its alias) in sui keystore.
     /// Any signature commits to a [struct IntentMessage] consisting of the Base64 encoded
     /// of the BCS serialized transaction bytes itself and its intent. If intent is absent,
     /// default will be used.

docs/content/guides/operator/validator-tasks.mdx

@@ -19,7 +19,7 @@ You can deploy Sui node in a number of ways.
 
 There are pre-built container images available in [Docker Hub](https://hub.docker.com/r/mysten/sui-node/tags).
 
-And pre built `linux/amd64` binaries available in S3 that you can can fetch using one of the following methods:
+And pre built `linux/amd64` binaries available in S3 that you can fetch using one of the following methods:
 
 ```shell
 wget https://releases.sui.io/$SUI_SHA/sui-node

docs/content/references/cli/keytool.mdx

@@ -34,7 +34,7 @@ Commands:
   multi-sig-combine-partial-sig-legacy
   show                              	Read the content at the provided file path. The accepted format can be [enum SuiKeyPair] (Base64 encoded of 33-byte `flag || privkey`)
                                         	or `type AuthorityKeyPair` (Base64 encoded `privkey`). It prints its Base64 encoded public key and the key scheme flag
-  sign                              	Create signature using the private key for for the given address in sui keystore. Any signature commits to a [struct IntentMessage]
+  sign                              	Create signature using the private key for the given address in sui keystore. Any signature commits to a [struct IntentMessage]
                                         	consisting of the Base64 encoded of the BCS serialized transaction bytes itself and its intent. If intent is absent, default will be
                                         	used
   sign-kms                          	Creates a signature by leveraging AWS KMS. Pass in a key-id to leverage Amazon KMS to sign a message and the base64 pubkey. Generate
@@ -149,7 +149,7 @@ Each command has its own help section. For example `sui keytool sign –help` di
 
 ```shell
 $ sui keytool sign --help
-Create signature using the private key for for the given address in sui keystore. Any signature commits to a [struct IntentMessage] consisting of the Base64 encoded of the BCS serialized
+Create signature using the private key for the given address in sui keystore. Any signature commits to a [struct IntentMessage] consisting of the Base64 encoded of the BCS serialized
 transaction bytes itself and its intent. If intent is absent, default will be used
 
 Usage: sui keytool sign [OPTIONS] --address <ADDRESS> --data <DATA>

external-crates/move/crates/move-analyzer/editors/code/README.md

@@ -26,7 +26,7 @@ binary stored in a different location.
 If you want to build, test, and trace Move code using the extension, you must install the `sui` binary on
 your machine - see [here](https://docs.sui.io/guides/developer/getting-started/sui-install) for
 instructions. The extension assumes that the `sui` binary is in your system path, but you can set
-its custom location location using VSCode's settings (`⌘` + `,` on macOS, or use the menu item *Code >
+its custom location using VSCode's settings (`⌘` + `,` on macOS, or use the menu item *Code >
 Preferences > Settings*). Search for the `move.sui.path` user setting, set it to the new location of
 the `sui` binary, and restart VSCode.
 

external-crates/move/crates/move-analyzer/trace-debug/README.md

@@ -29,7 +29,7 @@ Debugging a Move unit tests consists of two steps: generating a Move trace and a
 
 If you have [Mysten's Move extension](https://marketplace.visualstudio.com/items?itemName=mysten.move) installed you can generate a Move trace for tests defined in a given file by navigating to this file in VSCode and running `Move: Trace Move test execution` from the command palette. See the description of [Mysten's Move extension](https://marketplace.visualstudio.com/items?itemName=mysten.move) for pre-requisites needed to run this command.
 
-If you plan to use the the Trace Debugging Extension by itself, you need to generate the traces using command-line interface of `sui` binary. See [here](https://docs.sui.io/guides/developer/getting-started/sui-install) for instructions on how to install `sui` binary. Note that the `sui` binary must be built with the `tracing` feature flag. If your version of the `sui` binary was not built with this feature flag, an attempt to trace test execution will fail. In this case you may have to build the `sui` binary from source following these [instructions](https://docs.sui.io/guides/developer/getting-started/sui-install#install-sui-binaries-from-source).
+If you plan to use the Trace Debugging Extension by itself, you need to generate the traces using command-line interface of `sui` binary. See [here](https://docs.sui.io/guides/developer/getting-started/sui-install) for instructions on how to install `sui` binary. Note that the `sui` binary must be built with the `tracing` feature flag. If your version of the `sui` binary was not built with this feature flag, an attempt to trace test execution will fail. In this case you may have to build the `sui` binary from source following these [instructions](https://docs.sui.io/guides/developer/getting-started/sui-install#install-sui-binaries-from-source).
 
 Once the `sui` binary is installed, you generate traces for all test files in a given package by running the following command in the package's root directory:
 ```shell

external-crates/move/documentation/book/src/functions.md

@@ -316,7 +316,7 @@ fun add(x: u64, y: u64): u64 {
 The return value here is the result of `x + y`.
 
 [As mentioned above](#function-body), the function's body is an [expression block](./variables.md).
-The expression block can sequence various statements, and the final expression in the block will be
+The expression block can sequence various statements, and the final expression in the block will
 be the value of that block
 
 ```move

external-crates/move/documentation/book/src/packages.md

@@ -188,7 +188,7 @@ The `Move.lock` file is a TOML file that currently contains the following
 fields. 
 
 **Note**: other fields may be added to the lock file either in the future, or
-by third-party package package managers as well.
+by third-party package managers as well.
 
 ### The `[move]` Section
 
@@ -316,7 +316,7 @@ A named address `N` in a package `P` is in scope if:
 
 1. `P` declares a named address `N`; or
 2. A package in one of `P`'s transitive dependencies declares the named address `N` and there is a
-   dependency path in the package graph between between `P` and the declaring package of `N` with no
+   dependency path in the package graph between `P` and the declaring package of `N` with no
    renaming of `N`.
 
 Additionally, every named address in a package is exported. Because of this and the above scoping
@@ -352,7 +352,7 @@ module N::A {
 It is important to note that _renaming is not local_: once a named address `N` has been renamed to
 `N2` in a package `P` all packages that import `P` will not see `N` but only `N2` unless `N` is
 reintroduced from outside of `P`. This is why rule (2) in the scoping rules at the start of this
-section specifies a "dependency path in the package graph between between `P` and the declaring
+section specifies a "dependency path in the package graph between `P` and the declaring
 package of `N` with no renaming of `N`."
 
 ### Instantiating Named Addresses

external-crates/move/documentation/book/src/primitive-types.md

@@ -2,7 +2,7 @@
 
 The primitive types are the basic building blocks of the language.
 
-These primitive types can be used on their own or can be used be used to build more complex,
+These primitive types can be used on their own or can be used to build more complex,
 user-defined types, e.g. in a [`struct`](./structs.md).
 
 - [Integers](./primitive-types/integers.md)

sdk/docs/pages/dapp-kit/rpc-hooks.mdx

@@ -96,7 +96,7 @@ function MyComponent() {
 ## useSuiClientInfiniteQuery
 
 For RPC methods that support pagination, dApp Kit also implements a `useSuiClientInfiniteQuery`
-hook. For more details check out out the
+hook. For more details check out the
 [`useInfiniteQuery` documentation](https://tanstack.com/query/latest/docs/react/guides/infinite-queries).
 
 ```tsx

sdk/docs/pages/dapp-kit/wallet-hooks/useSignPersonalMessage.mdx

@@ -58,4 +58,4 @@ function MyComponent() {
 ## Result
 
 - `signature`: The signature of the message, as a `Base64`-encoded `string`.
-- `bytes`: The bytes of the message, as a a `Base64`-encoded `string`.
+- `bytes`: The bytes of the message, as a `Base64`-encoded `string`.

sdk/docs/pages/dapp-kit/wallet-hooks/useSignTransaction.mdx

@@ -71,7 +71,7 @@ function MyComponent() {
 ## Result
 
 - `signature`: The signature of the message, as a Base64-encoded `string`.
-- `bytes`: The serialized transaction bytes, as a a Base64-encoded `string`.
+- `bytes`: The serialized transaction bytes, as a Base64-encoded `string`.
 - `reportTransactionEffects`: A function to report the transaction effects to the wallet. This
   callback should always be invoked after executing the signed transaction. This function accepts
   the `rawEffects` returned from JSON-RPC `executeTransactionBlock` method, or the `effects.bcs`

sdk/docs/pages/typescript/migrations/sui-1.0.mdx

@@ -1,7 +1,7 @@
 # TS SDK v1.0 Migration Guide
 
 We are excited to announce the 1.0 release of the Typescript SDK. This release includes a lot of new
-features, as well as as number of renames, and cleanup of old APIs that no longer make sense.
+features, as well as number of renames, and cleanup of old APIs that no longer make sense.
 
 This migration guide will primarily focus on helping migrate existing features that have changed in
 this release, and won't cover all the new features that have been added, but here are some