JavaDocBou
diff --git a/‎docs/docs/api/auth/README.md‎
Lines changed: 1 addition & 1 deletion b/‎docs/docs/api/auth/README.md‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎docs/docs/api/rest/README.md‎
Lines changed: 13 additions & 13 deletions b/‎docs/docs/api/rest/README.md‎
Lines changed: 13 additions & 13 deletions
diff --git a/‎docs/docs/cli/install/README.md‎
Lines changed: 1 addition & 1 deletion b/‎docs/docs/cli/install/README.md‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎docs/docs/cli/login/README.md‎
Lines changed: 5 additions & 5 deletions b/‎docs/docs/cli/login/README.md‎
Lines changed: 5 additions & 5 deletions
diff --git a/‎docs/docs/cli/reference/README.md‎
Lines changed: 24 additions & 24 deletions b/‎docs/docs/cli/reference/README.md‎
Lines changed: 24 additions & 24 deletions
@@ -12,7 +12,7 @@ You'll find this API key in your [Account Settings](https://pipedream.com/settin
 
 Pipedream uses [Bearer Authentication](https://oauth.net/2/bearer-tokens/) to authorize your access to the API or SSE event streams. When you make API requests, pass an `Authorization` header of the following format:
 
-```text
+```
 Authorization: Bearer <api key>
 ```
 
 
@@ -18,7 +18,7 @@ The base URL for all requests is **{{$site.themeConfig.API_BASE_URL}}** .
 
 Pipedream uses [Bearer Authentication](https://oauth.net/2/bearer-tokens/) to authorize your access to the API. When you make API requests, pass an `Authorization` header of the following format:
 
-```text
+```
 Authorization: Bearer <api key>
 ```
 
@@ -151,7 +151,7 @@ Retrieve information on the authenticated user.
 
 **Endpoint**
 
-```text
+```
 GET /users/me
 ```
 
@@ -195,7 +195,7 @@ This route returns the components `id`, `code`, `configurable_props`, and other
 
 **Endpoint**
 
-```text
+```
 POST /components
 ```
 
@@ -267,7 +267,7 @@ Retrieve a component by ID to determine its metadata and configurable props.
 
 **Endpoint**
 
-```text
+```
 GET /components/{id}
 ```
 
@@ -329,7 +329,7 @@ curl https://api.pipedream.com/v1/components/sc_JDi8EB \
 
 **Endpoint**
 
-```text
+```
 GET /users/me/sources/
 ```
 
@@ -378,7 +378,7 @@ curl 'https://api.pipedream.com/v1/users/me/sources' \
 
 **Endpoint**
 
-```text
+```
 POST /sources/
 ```
 
@@ -459,7 +459,7 @@ Example response from creating an RSS source that runs once a minute:
 
 **Endpoint**
 
-```text
+```
 PUT /sources/{id}
 ```
 
@@ -511,7 +511,7 @@ Default: `true`.
 
 **Endpoint**
 
-```text
+```
 DELETE /sources/{id}
 ```
 
@@ -529,7 +529,7 @@ You can configure a source, or a workflow, to receive events from any number of
 
 **Endpoint**
 
-```text
+```
 POST /subscriptions?emitter_id={emitting_component_id}&listener_id={receiving_source_id}
 ```
 
@@ -574,21 +574,21 @@ Retrieve up to the last 100 events emitted by a source.
 
 **Endpoint**
 
-```text
+```
 GET /sources/{id}/event_summaries
 ```
 
 **Notes and Examples**
 
 The event data for events larger than `1KB` may get truncated in the response. If you're processing larger events, and need to see the full event data, pass `?expand=event`:
 
-```text
+```
 GET /sources/{id}/event_summaries?expand=event
 ```
 
 Pass `?limit=N` to retrieve the last **N** events:
 
-```text
+```
 GET /sources/{id}/event_summaries?limit=10
 ```
 
@@ -604,7 +604,7 @@ These IDs can be retrieved by using the [`GET /sources/{id}/event_summaries` end
 
 **Endpoint**
 
-```text
+```
 DELETE /sources/{id}/events
 ```
 
 
@@ -2,7 +2,7 @@
 
 To install the CLI, run:
 
-```text
+```bash
 curl https://cli.pipedream.com/install | sh
 ```
 
 
@@ -8,7 +8,7 @@ To start using the Pipedream CLI, you'll need to link it to your Pipedream accou
 
 If you already have a Pipedream account, run
 
-```text
+```
 pd login
 ```
 
@@ -18,7 +18,7 @@ Otherwise, you'll be asked to login.
 
 Once you're done, go back to your shell and you should see confirmation that your account is linked:
 
-```text
+```
 > pd login
 Logged in as dylburger (dylan@pipedream.com)
 ```
@@ -27,15 +27,15 @@ Logged in as dylburger (dylan@pipedream.com)
 
 If you haven't signed up for a Pipedream account, you can create an account using the CLI:
 
-```text
+```
 pd signup
 ```
 
 This will open up a new window in your default browser. You'll be asked to sign up for Pipedream here. Once you do, your account will be linked to the CLI, writing your API key for that account to your [`pd` config file](/cli/reference/#cli-config-file).
 
 Once you're done, go back to your shell and you should see confirmation that your account is linked:
 
-```text
+```
 > pd signup
 Logged in as dylburger (dylan@pipedream.com)
 ```
@@ -44,7 +44,7 @@ Logged in as dylburger (dylan@pipedream.com)
 
 You can log out of the CLI by running:
 
-```text
+```
 pd logout
 ```
 
 
@@ -14,7 +14,7 @@ Since this is a preview release, the commands you see below, and the [REST API](
 
 To install the CLI, run:
 
-```text
+```
 curl https://cli.pipedream.com/install | sh
 ```
 
@@ -34,7 +34,7 @@ We've also documented each command below, with usage examples for each.
 
 Everywhere you can refer to a specific source as an argument, you can use the source's ID _or_ its name slug. For example, to retrieve details about a specific source using `pd describe`, you can use either of the following commands:
 
-```text
+```
 λ ~/ pd describe dc_abc123
 
   id: dc_abc123
@@ -53,7 +53,7 @@ Searching for sources matching http
 
 Deletes an event source. Run:
 
-```text
+```
 pd describe <source-id-or-name>
 ```
 
@@ -69,13 +69,13 @@ When you select a source, we'll deploy it and start listening for new events.
 
 You can also deploy a specific source via Github URL:
 
-```text
+```
 pd deploy https://github.com/PipedreamHQ/pipedream/blob/master/components/http/http.js
 ```
 
 or author a component locally and deploy that local file:
 
-```text
+```
 pd deploy http.js
 ```
 
@@ -85,33 +85,33 @@ pd deploy http.js
 
 Display the details for a source: its id, name, and other configuration details:
 
-```text
+```
 pd describe <source-id-or-name>
 ```
 
 ### `pd events`
 
 Returns historical events sent to a source, and streams emitted events directly to the CLI.
 
-```text
+```
 pd events <source-id-or-name>
 ```
 
 By default, `pd events` prints (up to) the last 10 events sent to your source.
 
-```text
+```
 pd events -n 100 <source-id-or-name>
 ```
 
 `pd events -n N` retrieves the last `N` events sent to your source. We store the last 100 events sent to a source, so you can retrieve a max of 100 events using this command.
 
-```text
+```
 pd events -f <source-id-or-name>
 ```
 
 `pd events -f` connects to the [SSE stream tied to your source](/api/sse/) and displays events as the source produces them.
 
-```text
+```
 pd events -n N -f <source-id-or-name>
 ```
 
@@ -127,21 +127,21 @@ Lists Pipedream resources you own. Running `pd list` without any arguments promp
 
 You can also list specific resource types directly:
 
-```text
+```
 pd list sources
 ```
 
-```text
+```
 pd list streams
 ```
 
 `sources` and `streams` have shorter aliases, too:
 
-```text
+```
 pd list so
 ```
 
-```text
+```
 pd list st
 ```
 
@@ -157,7 +157,7 @@ Running `pd logout` without any arguments removes the default API key from your
 
 You can remove the API key for a specific profile by running:
 
-```text
+```
 pd logout -p <profile>
 ```
 
@@ -179,25 +179,25 @@ Updates the code, props, or metadata for an event source.
 
 If you deployed a source from Github, for example, someone might publish an update to that source, and you may want to run the updated code.
 
-```text
+```
 pd update <source-id-or-name> --code https://github.com/PipedreamHQ/pipedream/blob/master/components/http/http.js
 ```
 
 You can change the name of a source:
 
-```text
+```
 pd update <source-id-or-name> --name new-awesome-name
 ```
 
 You can deactivate a source if you want to stop it from running:
 
-```text
+```
 pd update <source-id-or-name> --deactivate
 ```
 
 or activate a source you previously deactivated:
 
-```text
+```
 pd update <source-id-or-name> --activate
 ```
 
@@ -209,19 +209,19 @@ Profiles allow you to work with multiple, named Pipedream accounts via the CLI.
 
 When you [login to the CLI](/cli/login/), the CLI writes the API key for that account to your config file, in the `api_key` field:
 
-```text
+```
 api_key = abc123
 ```
 
 You can set API keys for other, named profiles, too. Run
 
-```text
+```
 pd login -p <profile>
 ```
 
 `<profile>` can be any string of shell-safe characters that you'd like to use to identify this new profile. The CLI opens up a browser asking you to login to your target Pipedream account, then writes the API key to a section of the config file under this profile:
 
-```text
+```
 [your_profile]
 api_key = def456
 ```
@@ -232,15 +232,15 @@ You can also run `pd signup -p <profile>` if you'd like to sign up for a new Pip
 
 You can set a profile on any `pd` command by setting the `-p` or `--profile` flag. For example, to list the sources in a specific account, run:
 
-```text
+```
 pd list sources --profile <profile>
 ```
 
 ## Version
 
 To get the current version of the `pd` CLI, run
 
-```text
+```
 pd --version
 ```