Update terms (#209)

* update terms

access key -> API key
editor token -> session token

* update terms

access key -> API key

* remove extra space

Author: LauraLangdon

website/docs/how-to/customize-plugins/plugin-editor.md

@@ -14,9 +14,9 @@ The editor is hosted at `https://editor.suborbital.network`, and uses URL parame
 You will host the SE2 builder service in your cloud infrastructure with a configured DNS name. An HTTPS connection to the builder is required to use the editor.
 To launch the editor, you can either [embed the editor in a frame](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe) within your own webpage, or launch it in a new tab.
 
-## Editor token
+## Session token
 
-To authenticate the editor you'll need an [editor token](../../quickstart#obtain-an-editor-token).
+To authenticate the editor you'll need an [session token](../../quickstart#obtain-a-session-token).
 
 ## Configuration
 
@@ -32,7 +32,7 @@ Let's break it down:
 
 **Token**: `&token=K78as0aslwi30l8h5lbF4lS7`
 
-* The editor token retrieved from the control-plane service
+* The session token retrieved from the control-plane service
 
 **Ident**: `&ident=com.suborbital.customer`
 

website/docs/how-to/self-host-se2/deploy/other-deployments/minikube.md

@@ -172,7 +172,7 @@ Let’s tell minikube to forward requests to port 80 to our cluster!
 minikube tunnel
 ```
 
-### 8. Create an editor token
+### 8. Create a session token
 
 In order to test our editor, we’re going to come up with a plugin name, and create a token so we can access it!
 
@@ -206,7 +206,7 @@ Let’s install `curl`:
 apt update; apt install curl
 ```
 
-With `curl` installed, we can now get our editor token for testing:
+With `curl` installed, we can now get our session token for testing:
 
 ```bash
 curl [http://local.suborbital.network:8081/api/v1/token/<IDENT>/default/](http://local.suborbital.network:8081/api/v1/token/com.acmeco.gr9fas97234b/default/httpget)<PLUGIN_NAME>

website/docs/how-to/self-host-se2/self-hosted-quickstart.md

@@ -126,9 +126,9 @@ The `local.suborbital.network` subdomain points to `127.0.0.1`, i.e. `localhost`
 
 The SE2 plugin editor uses SE2's APIs from either [Go](./how-to/se2-go.md) or [JavaScript/TypeScript](./how-to/se2-js.md) to provide a low-friction environment for your users to write, build, test, and deploy plugins to your SE2 an instance in a single place.  Alternatively, the [Builder API](https://reference.suborbital.dev/) can be used programmatically, if that better suits your use case.
 
-### Obtain an editor token
+### Obtain a session token
 
-In addition to the `IDENTIFIER` and `ENV_TOKEN`, you’ll also need to set `NAMESPACE` and `fn` to the name of our namespace (e.g. `default`) and the name of our plugin (e.g. `hello`). Copy the `token` field in the response; this is your editor token.
+In addition to the `IDENTIFIER` and `ENV_TOKEN`, you’ll also need to set `NAMESPACE` and `fn` to the name of our namespace (e.g. `default`) and the name of our plugin (e.g. `hello`). Copy the `token` field in the response; this is your session token.
 
 ```bash
 curl --location --request GET "http://local.suborbital.network:8082/auth/v2/access/${IDENTIFIER}/${NAMESPACE}/${EXT}" \

website/docs/quickstart-with-demo.md

@@ -55,33 +55,33 @@ Here we can see a counter for plugin builds and build minutes. Both of these are
 
 ![Environment dashboard screen showing zero function builds and zero build minutes](../../website/static/img/env-dashboard-screen.png)
 
-## Create an access key
+## Create an API key
 
-Next, we'll need to create an access key. We'll click on:
+Next, we'll need to create an API key. We'll click on:
 
-- Manage access keys
-- Create new access key
+- Manage API keys
+- Create new API key
 
-Our integration will use this access key to provision resources and execute plugins in SE2. We'll give our access key:
+Our integration will use this API key to provision resources and execute plugins in SE2. We'll give our API key:
 
 - The name `DemoKey`
-- The description: `demo access key`
+- The description: `demo API key`
 
-![Access key creation screen with fields for name and description](../../website/static/img/create-access-key-screen.png)
+![API key creation screen with fields for name and description](../../website/static/img/create-access-key-screen.png)
 
 :::tip
-We'll only be shown this access key once, so we'll need to store it somewhere safe and secure!
+We'll only be shown this API key once, so we'll need to store it somewhere safe and secure!
 :::
 
 ## Integrate SE2 with our app
 
-We'll need to supply our environment variables (our environment access key and the name of our environment) to SE2. Within the directory we created when we cloned the repo for this demo in the [preliminary steps](#preliminary-steps), we'll:
+We'll need to supply our environment variables (our environment API key and the name of our environment) to SE2. Within the directory we created when we cloned the repo for this demo in the [preliminary steps](#preliminary-steps), we'll:
 
 - Open the `demo-proxyz` directory
 - Create a file named `.env`
 - Within our new `.env` file, we'll add our environment variables:
 
-  - `SUBORBITAL_TOKEN` is our environment's access key
+  - `SUBORBITAL_TOKEN` is our environment's API key
   - `SUBORBITAL_ENV` is the name we gave our environment
 
 - Next we'll need to export those variables by running:
@@ -106,9 +106,9 @@ Suborbital lets an application's users create their own secure, sandboxed plugin
 
 The SE2 plugin editor uses SE2's APIs from either [Go](./how-to/se2-go.md) or [JavaScript/TypeScript](./how-to/se2-js.md) to provide a low-friction environment for your users to write, build, test, and deploy plugins to your SE2 an instance in a single place.  Alternatively, the [Builder API](https://reference.suborbital.dev/) can be used programmatically, if that better suits your use case.
 
-### Obtain an editor token
+### Obtain a session token
 
-In addition to the `IDENTIFIER` and `ENV_TOKEN`, you’ll also need to set `NAMESPACE` and `fn` to the name of our namespace (e.g. `default`) and the name of our plugin (e.g. `hello`). Copy the `token` field in the response; this is your editor token.
+In addition to the `IDENTIFIER` and `ENV_TOKEN`, you’ll also need to set `NAMESPACE` and `fn` to the name of our namespace (e.g. `default`) and the name of our plugin (e.g. `hello`). Copy the `token` field in the response; this is your session token.
 
 ```bash
 curl --location --request GET "http://local.suborbital.network:8082/auth/v2/access/${IDENTIFIER}/${NAMESPACE}/${EXT}" \

website/docs/quickstart.md

@@ -59,7 +59,7 @@ Our integration will use this API key to provision resources and execute plugins
 - The name `DemoKey`
 - The description: `demo API key`
 
-![API key creation screen with fields for name and description](../../website/static/img/create-access-key-screen.png)
+![API key creation screen with fields for name and description](../../website/static/img/create-api-key-screen.png)
 
 :::tip
 We'll only be shown this API key once, so we'll need to store it somewhere safe and secure!
@@ -188,7 +188,7 @@ The SE2 plugin editor uses SE2's APIs from either [Go](./how-to/se2-go.md) or [J
 
 To grant a user access to modify a plugin, you'll need a session token. A session token is bound to a single plugin, and you'll create new tokens each time a user needs access to a plugin. To obtain a session token:
 
-<Tabs groupId='editor-token'>
+<Tabs groupId='session-token'>
 
 <TabItem value="go" label="Using Go">
 Call the `CreateSession` method with your tenant's name, the namespace, and the plugin name of your intended plugin. The response will be a struct that contains the session token. All tenant API methods will use this session response struct as input.

website/docs/reference/future-glossary.md

@@ -14,4 +14,4 @@ pagination_next: null
 | Tenant          | words | Identifies the relationship between an Environment and some specific user or collection of users interacting with it. The Environment administrator manages and identifies this relationship including, but not limited to, tenant authentication.                                                                                                                                             |   tnt                         |
 | Client | words | The application communicating with SE2 on the behalf of some Tenant |                            |
 | Environment Token     | words | Grants a Client access to an environment    |                            |
-| Editor Token  | words | Grants a Tenant access to the Builder Service                                                                                                                                     |                            |
+| Session Token  | words | Grants a Tenant access to the Builder Service                                                                                                                                     |                            |

website/docs/reference/glossary.md

@@ -12,4 +12,4 @@ pagination_next: null
 | Tenant          | Identifies the relationship between an Environment and some specific user or collection of users interacting with it. The Environment administrator manages and identifies this relationship including, but not limited to, tenant authentication.                                                                                                                                             |   tnt                         |
 | Client | The application communicating with SE2 on the behalf of some Tenant |                            |
 | Environment Token    | Grants a Client access to an environment    |                            |
-| Editor Token  | Grants a Tenant access to the Builder Service                                                                                                                                     |                            |
+| Session Token  | Grants a Tenant access to the Builder Service                                                                                                                                     |                            |