From 0a81e7ca16a55a681c200513d9877689ac8e6dfd Mon Sep 17 00:00:00 2001
From: Chang-Hung Liang <chang-hung.liang@zapier.com>
Date: Thu, 10 Oct 2024 20:52:27 +0800
Subject: [PATCH] Update invoke help doc

---
 docs/cli.html                             | 2 +-
 docs/cli.md                               | 2 +-
 packages/cli/docs/cli.html                | 2 +-
 packages/cli/docs/cli.md                  | 2 +-
 packages/cli/src/oclif/commands/invoke.js | 2 +-
 5 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/docs/cli.html b/docs/cli.html
index 08004b0f5..392c64c39 100644
--- a/docs/cli.html
+++ b/docs/cli.html
@@ -745,7 +745,7 @@ <h2 id="invoke">invoke</h2>
     <div class="col-md-5 col-sm-12 col-height  docs-primary">
       <blockquote>
 <p>Invoke an auth operation, a trigger, or a create/search action locally.</p>
-</blockquote><p><strong>Usage</strong>: <code>zapier invoke [ACTIONTYPE] [ACTIONKEY]</code></p><p>This command emulates how Zapier production environment would invoke your integration. It runs code locally, so you can use this command to quickly test your integration without deploying it to Zapier. This is especially useful for debugging and development.</p><p>This command loads environment variables and <code>authData</code> from the <code>.env</code> file in the current directory. If you don&apos;t have a <code>.env</code> file yet, you can use the <code>zapier invoke auth start</code> command to help you initialize it, or you can manually create it.</p><p>The <code>zapier invoke auth start</code> subcommand will prompt you for the necessary auth fields and save them to the <code>.env</code> file. For OAuth2, it will start a local HTTP server, open the browser, and wait for the OAuth2 redirect callback to get the access token.</p><p>Each line in the <code>.env</code> file should follow one of these formats:</p><ul>
+</blockquote><p><strong>Usage</strong>: <code>zapier invoke [ACTIONTYPE] [ACTIONKEY]</code></p><p>This command emulates how Zapier production environment would invoke your integration. It runs code locally, so you can use this command to quickly test your integration without deploying it to Zapier. This is especially useful for debugging and development.</p><p>This command loads environment variables and <code>authData</code> from the <code>.env</code> file in the current directory. If you don&apos;t have a <code>.env</code> file yet, you can use the <code>zapier invoke auth start</code> command to help you initialize it, or you can manually create it.</p><p>The <code>zapier invoke auth start</code> subcommand will prompt you for the necessary auth fields and save them to the <code>.env</code> file. For OAuth2, it will start a local HTTP server, open the authorization URL in the browser, wait for the OAuth2 redirect, and get the access token.</p><p>Each line in the <code>.env</code> file should follow one of these formats:</p><ul>
 <li><code>VAR_NAME=VALUE</code> for environment variables</li>
 <li><code>authData_FIELD_KEY=VALUE</code> for auth data fields</li>
 </ul><p>For example, a <code>.env</code> file for an OAuth2 integration might look like this:</p>
diff --git a/docs/cli.md b/docs/cli.md
index 89bffed9f..10a9de7b8 100644
--- a/docs/cli.md
+++ b/docs/cli.md
@@ -309,7 +309,7 @@ This command emulates how Zapier production environment would invoke your integr
 
 This command loads environment variables and `authData` from the `.env` file in the current directory. If you don't have a `.env` file yet, you can use the `zapier invoke auth start` command to help you initialize it, or you can manually create it.
 
-The `zapier invoke auth start` subcommand will prompt you for the necessary auth fields and save them to the `.env` file. For OAuth2, it will start a local HTTP server, open the browser, and wait for the OAuth2 redirect callback to get the access token.
+The `zapier invoke auth start` subcommand will prompt you for the necessary auth fields and save them to the `.env` file. For OAuth2, it will start a local HTTP server, open the authorization URL in the browser, wait for the OAuth2 redirect, and get the access token.
 
 Each line in the `.env` file should follow one of these formats:
 
diff --git a/packages/cli/docs/cli.html b/packages/cli/docs/cli.html
index 08004b0f5..392c64c39 100644
--- a/packages/cli/docs/cli.html
+++ b/packages/cli/docs/cli.html
@@ -745,7 +745,7 @@ <h2 id="invoke">invoke</h2>
     <div class="col-md-5 col-sm-12 col-height  docs-primary">
       <blockquote>
 <p>Invoke an auth operation, a trigger, or a create/search action locally.</p>
-</blockquote><p><strong>Usage</strong>: <code>zapier invoke [ACTIONTYPE] [ACTIONKEY]</code></p><p>This command emulates how Zapier production environment would invoke your integration. It runs code locally, so you can use this command to quickly test your integration without deploying it to Zapier. This is especially useful for debugging and development.</p><p>This command loads environment variables and <code>authData</code> from the <code>.env</code> file in the current directory. If you don&apos;t have a <code>.env</code> file yet, you can use the <code>zapier invoke auth start</code> command to help you initialize it, or you can manually create it.</p><p>The <code>zapier invoke auth start</code> subcommand will prompt you for the necessary auth fields and save them to the <code>.env</code> file. For OAuth2, it will start a local HTTP server, open the browser, and wait for the OAuth2 redirect callback to get the access token.</p><p>Each line in the <code>.env</code> file should follow one of these formats:</p><ul>
+</blockquote><p><strong>Usage</strong>: <code>zapier invoke [ACTIONTYPE] [ACTIONKEY]</code></p><p>This command emulates how Zapier production environment would invoke your integration. It runs code locally, so you can use this command to quickly test your integration without deploying it to Zapier. This is especially useful for debugging and development.</p><p>This command loads environment variables and <code>authData</code> from the <code>.env</code> file in the current directory. If you don&apos;t have a <code>.env</code> file yet, you can use the <code>zapier invoke auth start</code> command to help you initialize it, or you can manually create it.</p><p>The <code>zapier invoke auth start</code> subcommand will prompt you for the necessary auth fields and save them to the <code>.env</code> file. For OAuth2, it will start a local HTTP server, open the authorization URL in the browser, wait for the OAuth2 redirect, and get the access token.</p><p>Each line in the <code>.env</code> file should follow one of these formats:</p><ul>
 <li><code>VAR_NAME=VALUE</code> for environment variables</li>
 <li><code>authData_FIELD_KEY=VALUE</code> for auth data fields</li>
 </ul><p>For example, a <code>.env</code> file for an OAuth2 integration might look like this:</p>
diff --git a/packages/cli/docs/cli.md b/packages/cli/docs/cli.md
index 89bffed9f..10a9de7b8 100644
--- a/packages/cli/docs/cli.md
+++ b/packages/cli/docs/cli.md
@@ -309,7 +309,7 @@ This command emulates how Zapier production environment would invoke your integr
 
 This command loads environment variables and `authData` from the `.env` file in the current directory. If you don't have a `.env` file yet, you can use the `zapier invoke auth start` command to help you initialize it, or you can manually create it.
 
-The `zapier invoke auth start` subcommand will prompt you for the necessary auth fields and save them to the `.env` file. For OAuth2, it will start a local HTTP server, open the browser, and wait for the OAuth2 redirect callback to get the access token.
+The `zapier invoke auth start` subcommand will prompt you for the necessary auth fields and save them to the `.env` file. For OAuth2, it will start a local HTTP server, open the authorization URL in the browser, wait for the OAuth2 redirect, and get the access token.
 
 Each line in the `.env` file should follow one of these formats:
 
diff --git a/packages/cli/src/oclif/commands/invoke.js b/packages/cli/src/oclif/commands/invoke.js
index 094bd76f5..452a7d6f8 100644
--- a/packages/cli/src/oclif/commands/invoke.js
+++ b/packages/cli/src/oclif/commands/invoke.js
@@ -1157,7 +1157,7 @@ This command emulates how Zapier production environment would invoke your integr
 
 This command loads environment variables and \`authData\` from the \`.env\` file in the current directory. If you don't have a \`.env\` file yet, you can use the \`zapier invoke auth start\` command to help you initialize it, or you can manually create it.
 
-The \`zapier invoke auth start\` subcommand will prompt you for the necessary auth fields and save them to the \`.env\` file. For OAuth2, it will start a local HTTP server, open the browser, and wait for the OAuth2 redirect callback to get the access token.
+The \`zapier invoke auth start\` subcommand will prompt you for the necessary auth fields and save them to the \`.env\` file. For OAuth2, it will start a local HTTP server, open the authorization URL in the browser, wait for the OAuth2 redirect, and get the access token.
 
 Each line in the \`.env\` file should follow one of these formats: