diff --git a/alerts/configuring-alert-destinations/configuring-alert-destinations.md b/alerts/configuring-alert-destinations/configuring-alert-destinations.md index c0e1687..b701b9a 100644 --- a/alerts/configuring-alert-destinations/configuring-alert-destinations.md +++ b/alerts/configuring-alert-destinations/configuring-alert-destinations.md @@ -50,14 +50,14 @@ Tenderly keeps track of all executions. Webhook execution can have several statu * **Success** - indicates that the webhook was successfully executed and the event was delivered to the specified URL * **Failed** - indicates that the webhook was unable to be executed due to an error, such as a connectivity issue, a problem with the URL, or something else (check the response content to see what caused the error or contact our support) * **Pending** - indicates that the webhook is in the process of being executed and has not yet been completed -* **Retry** - indicates that the webhook execution failed but will be retried no more than 5 times until it changes the status to Sucess or Failed +* **Retry** - indicates that the webhook execution failed but will be retried no more than 5 times until it changes the status to Success or Failed * **Skipped** - indicates that the webhook was not executed because it was disabled #### Webhook payload The webhook will receive the payload representing the alerting event. The payload consists of three fields: -* **id**: `String` - ID unique accross all delivered alert events (UUID). +* **id**: `String` - ID unique across all delivered alert events (UUID). * **event\_type**: `TEST` | `ALERT` - the type of webhook event type. * **transaction**: `Object` - an object representing an un-decoded transaction that triggered the alert and the webhook execution. diff --git a/alerts/tutorials-and-quickstarts/how-to-use-webhooks-for-alerting.md b/alerts/tutorials-and-quickstarts/how-to-use-webhooks-for-alerting.md index 559fb6a..2d23745 100644 --- a/alerts/tutorials-and-quickstarts/how-to-use-webhooks-for-alerting.md +++ b/alerts/tutorials-and-quickstarts/how-to-use-webhooks-for-alerting.md @@ -69,7 +69,7 @@ Webhook execution can have several statuses: * **Success:** Webhook was successfully executed, and the event was delivered to the specified URL. * **Failed**: Webhook was unable to be executed due to an error, such as a connectivity issue, a problem with the URL, or something else. Check the response content to see what caused the error, or contact our support. * **Pending**: Webhook is in the process of being executed and has not yet been completed. -* **Retry**: Webhook execution failed but will be retried no more than 5 times until it changes the status to Sucess or Failed. +* **Retry**: Webhook execution failed but will be retried no more than 5 times until it changes the status to Success or Failed. * **Skipped**: Webhook was not executed because it was disabled.

Webhook Execution Page

diff --git a/debugger/how-to-use-tenderly-debugger/README.md b/debugger/how-to-use-tenderly-debugger/README.md index 07465bd..09a2537 100644 --- a/debugger/how-to-use-tenderly-debugger/README.md +++ b/debugger/how-to-use-tenderly-debugger/README.md @@ -1,6 +1,6 @@ # How to use Tenderly Debugger -The Visual Debugger is one of the tools people love the most. Instead of wasting countless hours debugging transactions, you can use the Visual Debugger so you can focus more on buidling and less on scratching your head. +The Visual Debugger is one of the tools people love the most. Instead of wasting countless hours debugging transactions, you can use the Visual Debugger so you can focus more on building and less on scratching your head. **The level of detail present here doesn't exist anywhere else and reduces development time by orders of magnitude**. diff --git a/devnets/advanced/automated-devnet-spawning-bash-and-javascript.md b/devnets/advanced/automated-devnet-spawning-bash-and-javascript.md index e8152a9..d7c3e66 100644 --- a/devnets/advanced/automated-devnet-spawning-bash-and-javascript.md +++ b/devnets/advanced/automated-devnet-spawning-bash-and-javascript.md @@ -59,7 +59,7 @@ You will find two directories with code for spawning DevNets: a bash (`spawn-dev ```bash TENDERLY_ACCESS_KEY=your_access_key TENDERLY_PROJECT_SLUG=your_project_slug - TENDERLY_DEVNET_TEMPLATE=your_devnet_tempalte + TENDERLY_DEVNET_TEMPLATE=your_devnet_template TENDERLY_ACCOUNT_ID=your_account_id ``` 3. To run the script, use the following command in your terminal: diff --git a/monitoring/integrations.md b/monitoring/integrations.md index 82a93b8..6de72bb 100644 --- a/monitoring/integrations.md +++ b/monitoring/integrations.md @@ -651,7 +651,7 @@ contract('Calculator', function (accounts) { error = e; } - assert.isDefined(error, "No exception thrown during divison"); + assert.isDefined(error, "No exception thrown during division"); assert.isTrue(error.message.search("revert") >= 0, "Expected transaction revert"); }); }); diff --git a/tenderly-sandbox.md b/tenderly-sandbox.md index 6234c35..711afc8 100644 --- a/tenderly-sandbox.md +++ b/tenderly-sandbox.md @@ -67,7 +67,7 @@ If you don’t create a copy, any changes you make to someone else’s Sandbox w #### Managing your Sandboxes -To view a list of all the Sandboxes you created or copied, **click on the dropdown menu** next to the logo in the top nav bar. By default, all Sandboxes are publicaly visible. +To view a list of all the Sandboxes you created or copied, **click on the dropdown menu** next to the logo in the top nav bar. By default, all Sandboxes are publicly visible. Manage your Sandboxes by **clicking the three dots icon** next to the Sandbox name to perform any of the following actions: diff --git a/web3-gateway/references/brief-json-rpc.md b/web3-gateway/references/brief-json-rpc.md index ae339d8..733a3c0 100644 --- a/web3-gateway/references/brief-json-rpc.md +++ b/web3-gateway/references/brief-json-rpc.md @@ -5,7 +5,7 @@ description: A brief overview of supported Ethereum JSON RPC calls. # Brief JSON RPC reference {% hint style="info" %} -This page shows a brief overview of supported Ethereum JSON RPC calls. Find a [detaild list of supported calls](detailed-json-rpc.md). +This page shows a brief overview of supported Ethereum JSON RPC calls. Find a [detailed list of supported calls](detailed-json-rpc.md). {% endhint %} ### `eth_getBlockByHash`