Skip to content

Commit ba3da24

Browse files
authored
Fixing typos (#1412)
1 parent 5d2314a commit ba3da24

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

examples/chatgpt/gpt_actions_library/gpt_action_snowflake_direct.ipynb

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@
2727
"source": [
2828
"This particular GPT Action provides an overview of how to connect to a Snowflake Data Warehouse. This Action takes a user’s question, scans the relevant tables to gather the data schema, then writes a SQL query to answer the user’s question.\n",
2929
"\n",
30-
"Note: This cookbook return back a [ResultSet SQL statement](https://docs.snowflake.com/en/developer-guide/sql-api/handling-responses#getting-the-data-from-the-results), rather than the full result that is not limited by GPT Actions application/json payload limit. For production and advanced use-case, a middleware is required to return back a CSV file. You can follow instructions in the [GPT Actions - Snowflake Middleware cookbook](../gpt_action_snowflake_middleware) to implement this flow instead."
30+
"Note: This cookbook returns back a [ResultSet SQL statement](https://docs.snowflake.com/en/developer-guide/sql-api/handling-responses#getting-the-data-from-the-results), rather than the full result that is not limited by GPT Actions application/json payload limit. For production and advanced use-case, a middleware is required to return back a CSV file. You can follow instructions in the [GPT Actions - Snowflake Middleware cookbook](../gpt_action_snowflake_middleware) to implement this flow instead."
3131
]
3232
},
3333
{
@@ -42,7 +42,7 @@
4242
"metadata": {},
4343
"source": [
4444
"\n",
45-
"Value: Users can now leverage ChatGPT's natural language capability to connect directly to Snowflake’s Data Warehouse..\n",
45+
"Value: Users can now leverage ChatGPT's natural language capability to connect directly to Snowflake’s Data Warehouse.\n",
4646
"\n",
4747
"Example Use Cases:\n",
4848
"\n",
@@ -282,7 +282,7 @@
282282
"cell_type": "markdown",
283283
"metadata": {},
284284
"source": [
285-
"### 2. Set up the Securit Integration\n",
285+
"### 2. Set up the Security Integration\n",
286286
"* Review the Snowflake OAuth Overview: [https://docs.snowflake.com/en/user-guide/oauth-snowflake-overview](https://docs.snowflake.com/en/user-guide/oauth-snowflake-overview)\n",
287287
"* Create new OAuth credentials through a [Security Integration](https://docs.snowflake.com/en/sql-reference/sql/create-security-integration-oauth-snowflake) - you will need a new one for each OAuth app/custom GPT since Snowflake Redirect URIs are 1-1 mapped to Security Integrations"
288288
]
@@ -373,7 +373,7 @@
373373
"\n",
374374
"You’ll find the Client Secret in OAUTH_CLIENT_SECRET. Do not include the double quotes when copying the value.\n",
375375
"\n",
376-
"Now is a good time to [test your Snowflake integration in Postman](https://community.snowflake.com/s/article/How-to-configure-postman-for-testing-SQL-API-with-OAuth). If you copnfigured a network policy for your security integration, ensure that it includes the IP of the machine you're using to test."
376+
"Now is a good time to [test your Snowflake integration in Postman](https://community.snowflake.com/s/article/How-to-configure-postman-for-testing-SQL-API-with-OAuth). If you configured a network policy for your security integration, ensure that it includes the IP of the machine you're using to test."
377377
]
378378
},
379379
{

0 commit comments

Comments
 (0)