chore(docs): project_environment -> environment_name (before client-create environment fully lands)

Author: tjk

docs-v2/pages/connect/api.mdx

@@ -224,7 +224,7 @@ Pipedream will send events on successful auth, or any errors, to this URL via we
 
 ---
 
-`project_environment` **string** (_optional_)
+`environment_name` **string** (_optional_)
 
 Specify the environment (`production` or `development`) to use for the account connection flow. Defaults to `production`.
 
@@ -933,4 +933,4 @@ curl -X POST https://api.pipedream.com/v1/connect/{project_id}/info \
   -H "Authorization: Bearer {access_token}" \
 ```
 </Tabs.Tab>
-</Tabs>
+</Tabs>

docs-v2/pages/connect/environments.mdx

@@ -7,4 +7,4 @@ Pipedream Connect projects support two environments: `development` and `producti
 
 ## How to specify environment
 
-You specify the environment when [creating a new Connect token](/connect/api/#create-a-new-token) with the Pipedream SDK or API. By default, the enviromment is set to `production`. When users succesfully connect their account, Pipedream saves it for that `external_user_id` in the specified `project_environment`.
+You specify the environment when [creating a new Connect token](/connect/api/#create-a-new-token) with the Pipedream SDK or API. By default, the enviromment is set to `production`. When users succesfully connect their account, Pipedream saves it for that `external_user_id` in the specified `environment_name`.

docs-v2/pages/connect/tokens.mdx

@@ -21,6 +21,6 @@ When you generate a token, you can specify a `webhook_uri` where Pipedream will
 
 ## Tokens are scoped to end users and project environments
 
-When you [create a new Connect token](/connect/api/#create-a-new-token), you pass an `external_user_id` and an optional `project_environment` parameter. By default, the environment is set to `production`. See the docs on [environments](/connect/environments) for more information.
+When you [create a new Connect token](/connect/api/#create-a-new-token), you pass an `external_user_id` and an optional `environment_name` parameter. By default, the environment is set to `production`. See the docs on [environments](/connect/environments) for more information.
 
-Tokens are scoped to this user and environment. When the user successfully connects an account with that token, it will be saved for that `external_user_id` in the specified `project_environment`.
+Tokens are scoped to this user and environment. When the user successfully connects an account with that token, it will be saved for that `external_user_id` in the specified `environment_name`.

packages/sdk/src/server/index.ts

@@ -88,7 +88,7 @@ export type ConnectTokenOpts = {
    * Specify the environment ("production" or "development") to use for the
    * account connection flow. Defaults to "production".
    */
-  project_environment?: string;
+  environment_name?: string;
 };
 
 export type AppInfo = {