GitBook: No commit message

Author: Addison Schultz

docs/getting-started/development.md

@@ -21,7 +21,7 @@ By default (defined in the CLI-generated `gitbook-manifest.yaml`), your integrat
 
 After publishing your integration, the CLI will give you a link to install your integration into the organization you’ve set.
 
-You need to install your app into at least 1 space or organization in order to develop it locally. Make sure to note the `spaceId` of the space you're installing it into for step 2.
+You need to install your app into at least 1 space or organization in order to develop it locally. 
 {% endstep %}
 
 {% step %}
@@ -30,17 +30,15 @@ You need to install your app into at least 1 space or organization in order to d
 While inside the root directory of your app, run:
 
 ```
-gitbook dev <spaceId>
+gitbook dev
 ```
 
-This will start a development server tied to the space specified in the command.
-
-After running the command, the CLI will generate a `gitbook-dev.yaml` file that contains the `spaceId` needed to establish the connection while you continue to develop your app. You can change this at any time in by re-running `gitbook dev <spaceId>`.
+This will start a development server tied to your organization.
 
 {% hint style="info" %}
 Running this command will start a development server for use by the integration only. **You do not need to navigate to the port the server is running on.** \
 \
-All integration traffic to the specified space will automatically be served from your local server instead of the published version.
+All integration traffic will automatically be served from your local server instead of the published version.
 {% endhint %}
 {% endstep %}
 

docs/getting-started/setup-guide.md

@@ -62,18 +62,14 @@ In order to develop your integration on your local machine, you’ll first need
 gitbook publish
 ```
 
-This will publish your app to GitBook, and return a link with which you can install your integration. Install your integration into a space, and note the `spaceId` in the URL.
+This will publish your app to GitBook, and return a link with which you can install your integration. After installing your integration into your organization, space, or site, you can then run the development command to work on your integration locally.
 
 Return to your integration on your local machine, and in the root of the integration, run the following development command:
 
 ```bash
-gitbook dev spaceId
+gitbook dev
 ```
 
-{% hint style="info" %}
-Example: If your integration is installed in a space [`https://app.gitbook.com/o/1234/s/5678/`](https://app.gitbook.com/s/yPzlUas0Q5RLUIZ0s3Cl/integrations/development-environment), your `spaceId` would be `5678`.
-{% endhint %}
-
 After running the development script, you’re ready to start building your integration! Any changes made in your local version of the integration will be sent to the space you have your integration installed in. You’ll also be able to see logs in your console where applicable.
 
 Read more on development and publishing concepts:

docs/integrations/reference.md

@@ -20,9 +20,9 @@ The token can also be provided using the command line argument `--token=<token>`
 
 Create and initialize a new integration locally. The program will prompt for information about the integration.
 
-### `gitbook dev <spaceId>`
+### `gitbook dev`
 
-Create a live connection with a space within your GitBook organization. Updates made locally while the connection is running will automatically be received in the chosen space.&#x20;
+Create a live connection from your integration to your GitBook editor. Updates made locally while the connection is running will automatically be received in the editor.&#x20;
 
 See the [development section](../getting-started/development.md) to learn more.