From 805d2f0b8381e8ec5ce3bf4234c10153a19a197b Mon Sep 17 00:00:00 2001 From: Jonathan Cobb Date: Mon, 23 Nov 2020 12:45:18 -0500 Subject: [PATCH] update docs --- docs/launch-types.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/launch-types.md b/docs/launch-types.md index 52a55be6..f9da6f0a 100644 --- a/docs/launch-types.md +++ b/docs/launch-types.md @@ -21,15 +21,14 @@ When using the API, set the `launchType` property in the JSON object that create The two key distinguishing characteristics of each Launch Type are its **Mode** and how it handles **Cloud Services**. ### Bubble Mode -The mode can be either `sage` or `node`. +The mode can be either `sage` or `node`, and +is called `installType` in the [API](https://github.com/getbubblenow/bubble-docs/blob/master/api/README.md). A `sage`, also called a launcher, is a Bubble that launches other Bubbles. You don't connect devices to a sage/launcher. You just launcher other Bubbles with it. A `node`, also often just called a Bubble, is a regular Bubble that acts as a VPN and you connect devices to it. -The mode is called `installType` in the [API](https://github.com/getbubblenow/bubble-docs/blob/master/api/README.md). - ### Cloud Services A bubble will either delegate cloud services back to the launcher that created it, or use the cloud services directly itself.