Fix typos (#2901)

* fix typo * fix typos * fix typo * fix typo * fix typo
ecadlabs · Apr 9, 2024 · 81691c9 · 81691c9
1 parent f489c39
commit 81691c9
Show file tree

Hide file tree

Showing 5 changed files with 7 additions and 7 deletions.
diff --git a/docs/increase_paid_storage.md b/docs/increase_paid_storage.md
@@ -22,7 +22,7 @@ const op = await Tezos.contract.increasePaidStorage({
 
 await op.confirmation();
 ```
-- `amount` is the the number of `bytes` you want to increase the paid storage by
+- `amount` is the number of `bytes` you want to increase the paid storage by
 - `destination` is the `KT1` address of the smart contract which storage you would like to increase
 
 After waiting for the operation confirmation, you will also have access to various getters of the operation such as `status`, `amount`, `destination`, `fee`, `gasLimit`, `errors`, `storageLimit`, `consumedMilligas`.
@@ -105,4 +105,4 @@ const batch = await Tezos.wallet
 
 const op = await batch.send();
 await op.confirmation();
-```
+```
diff --git a/docs/smart_rollups.md b/docs/smart_rollups.md
@@ -30,7 +30,7 @@ await op.confirmation();
 - `kernel` is passed as a hexadecimal string examples can be found at [this tezos docs endpoint](https://tezos.gitlab.io/active/smart_rollups.html)
 - `parametersType` is a MichelsonV1Expression to define the type.
 
-For more information in regards to Smart Rollup Origination please refer to the this [link](https://tezos.gitlab.io/active/smart_rollups.html#origination)
+For more information in regards to Smart Rollup Origination please refer to this [link](https://tezos.gitlab.io/active/smart_rollups.html#origination)
 
 
 ## `smart_rollup_add_messages`
@@ -76,7 +76,7 @@ You may obtain the serialized output proof and commitment hash through an RPC ca
 `<smart-rollup-node-base-url>/global/block/head/helpers/proofs/outbox/${outboxMessageLevel}/messages?index=${outboxMessageIndex}`
 Where:
 * `outboxMessageLevel` is the Tezos level of the outbox message;
-* `outboxMessageIndex` is the index (number) of the the outbox message.
+* `outboxMessageIndex` is the index (number) of the outbox message.
 
 The outbox message can only be executed when the corresponding commitment is cemented.
 

diff --git a/docs/version.md b/docs/version.md
@@ -1315,7 +1315,7 @@ The `RPCRunOperationParam` parameter has new optional properties: `self`, `unpar
 
 Added support to forge and unforge the new operation kinds `transfer_ticket`, `tx_rollup_origination` and `tx_rollup_submit_batch` related to TORU. We plan to add support for the remaining operations in a subsequent release.
 
-## `@taquito/michelson-encoder` - Added support for the the new type`tx_rollup_l2_address`
+## `@taquito/michelson-encoder` - Added support for the new type`tx_rollup_l2_address`
 
 We created a new class `TxRollupL2AddressToken` in the michelson-encoder to support the new Michelson type `tx_rollup_l2_address`. This type is used to identify accounts on transaction rollups' ledgers. Those accounts are prefixed with `tz4`.
 The `TxRollupL2AddressToken` class allows users of Taquito to pass `tz4` addresses in storage or smart contract entry points using the Taquito JS abstraction.

diff --git a/packages/taquito-rpc/src/rpc-client-modules/rpc-cache.ts b/packages/taquito-rpc/src/rpc-client-modules/rpc-cache.ts
@@ -882,7 +882,7 @@ export class RpcClientCache implements RpcClientInterface {
    * @param data Data to pack
    * @param options contains generic configuration for rpc calls to specified block (default to head)
    * @description Computes the serialized version of a data expression using the same algorithm as script instruction PACK
-   * Note: You should always verify the packed bytes before signing or requesting that they be signed when using the the RPC to pack.
+   * Note: You should always verify the packed bytes before signing or requesting that they be signed when using the RPC to pack.
    * This precaution helps protect you and your applications users from RPC nodes that have been compromised.
    * A node that is operated by a bad actor, or compromised by a bad actor could return a fully formed operation that does not correspond to the input provided to the RPC endpoint.
    * A safer solution to pack and sign data would be to use the `packDataBytes` function available in the `@taquito/michel-codec` package.

diff --git a/packages/taquito-rpc/src/taquito-rpc.ts b/packages/taquito-rpc/src/taquito-rpc.ts
@@ -886,7 +886,7 @@ export class RpcClient implements RpcClientInterface {
    * @param data Data to pack
    * @param options contains generic configuration for rpc calls to specified block (default to head)
    * @description Computes the serialized version of a data expression using the same algorithm as script instruction PACK
-   * Note: You should always verify the packed bytes before signing or requesting that they be signed when using the the RPC to pack.
+   * Note: You should always verify the packed bytes before signing or requesting that they be signed when using the RPC to pack.
    * This precaution helps protect you and your applications users from RPC nodes that have been compromised.
    * A node that is operated by a bad actor, or compromised by a bad actor could return a fully formed operation that does not correspond to the input provided to the RPC endpoint.
    * A safer solution to pack and sign data would be to use the `packDataBytes` function available in the `@taquito/michel-codec` package.