From 84f4bbb37c4b209a0f9311dac2de70b610fa9e56 Mon Sep 17 00:00:00 2001 From: deterclosed <164524498+deterclosed@users.noreply.github.com> Date: Wed, 18 Dec 2024 07:26:08 +0800 Subject: [PATCH] chore: fix some typos in comment (#3094) Signed-off-by: deterclosed --- docs/contract-test-collection.md | 2 +- integration-tests/data/metadataViews.ts | 2 +- integration-tests/data/smartpy-example-contract.ts | 2 +- packages/taquito-beacon-wallet/src/errors.ts | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/contract-test-collection.md b/docs/contract-test-collection.md index 2043138481..4a332a12f5 100644 --- a/docs/contract-test-collection.md +++ b/docs/contract-test-collection.md @@ -1367,7 +1367,7 @@ license: MIT Transactions to smart contracts operate in the same fashion as transactions to an implicit account, the only difference being the `KT1...` address. You will also receive a transaction hash and have to wait for the transaction to be confirmed. Once confirmed, it can be the right time to update the user's/contract's balance, for example. -Sending a transaction to a smart contract to update its storage will be a different type of action as it implies targetting a specific entrypoint and formatting correctly the data to be sent. +Sending a transaction to a smart contract to update its storage will be a different type of action as it implies targeting a specific entrypoint and formatting correctly the data to be sent. Fortunately, Taquito will make this operation go like a breeze! First, you need the contract abstraction created with the address of the smart contract you are targeting: diff --git a/integration-tests/data/metadataViews.ts b/integration-tests/data/metadataViews.ts index 6f084448a8..791061b87a 100644 --- a/integration-tests/data/metadataViews.ts +++ b/integration-tests/data/metadataViews.ts @@ -349,7 +349,7 @@ export const metadataViewsExample2 = { }, code: [ { prim: 'CAR', args: [], annots: [] } ], annotations: [ - { name: '%arg_zero', description: 'This is obvioulsy ignored.' }, + { name: '%arg_zero', description: 'This is obviously ignored.' }, { name: '%arg_one', description: 'This is also ignored, but different.' }, { name: '%arg_one_result', description: 'This is %arg_one on the resulting side.' }, { diff --git a/integration-tests/data/smartpy-example-contract.ts b/integration-tests/data/smartpy-example-contract.ts index 6b4f822cd8..cfed1f6211 100644 --- a/integration-tests/data/smartpy-example-contract.ts +++ b/integration-tests/data/smartpy-example-contract.ts @@ -1,4 +1,4 @@ -// This contract code has storage,parameter,code but the Tezos RPC expects parmeter,code,storage +// This contract code has storage,parameter,code but the Tezos RPC expects parameter,code,storage export const smartpySample = [{"prim":"storage","args":[ {"prim":"nat"}] }, diff --git a/packages/taquito-beacon-wallet/src/errors.ts b/packages/taquito-beacon-wallet/src/errors.ts index 471dbbfa2f..ce719f84d5 100644 --- a/packages/taquito-beacon-wallet/src/errors.ts +++ b/packages/taquito-beacon-wallet/src/errors.ts @@ -16,7 +16,7 @@ export class BeaconWalletNotInitialized extends PermissionDeniedError { /** * @category Error - * @description Error that indicates missing required persmission scopes + * @description Error that indicates missing required permission scopes */ export class MissingRequiredScopes extends PermissionDeniedError { constructor(public readonly requiredScopes: PermissionScope[]) {