docs: Update headings for new style rule (#3396)

* docs: Update headings for new style rule

* docs: Fix headings - Get started

* docs: Fix headings - Install

* docs: Fix headings - Concepts

* docs: Fix typos

* docs: Fix headings - Configuration

* docs: Fix headings - Operations

* docs: Fix headings - Troubleshoot

* docs: Fix headings - Clients and Develop

* docs: Fix headings - HCP and ENT

* docs: Fix headings - Release notes

* docs: Fix typos

* docs: Fix capitalization in TOC
This commit is contained in:
Dan Heath authored and GitHub committed 2023-07-07 14:42:11 -04:00
1 parent 96d2531fbb
commit 3f4cd53d16
94 files changed
+452 -436

No files matched your search

@@ -49,7 +49,7 @@ The dev-mode default target allows you to make as many connections as you want
within the authorized session. When you are finished making connections, simply
`Ctrl-C/Command-C` the `boundary connect` process to shut down the session.
### Using Connect Helpers
## Use connect helpers
Boundary includes connect helpers that automatically accept host SSH key prompts
for you. These are written as `boundary connect <subcommand>`.
@@ -82,7 +82,7 @@ specify a username other than your currently logged-in user. This ensures that
regardless of your `-style` choice, the username is properly passed to the
executed client, and you don't need to figure out the syntax yourself.
## Selecting Targets
## Select targets
When using `boundary connect` you must identify the target used for connecting.
Convention in this documentation is to use the target ID because it refers to a
@@ -103,7 +103,7 @@ Here is an SSH example in dev mode:
$ boundary connect ssh -target-name "Generated target" -target-scope-name "Generated project scope"
```
## Built-In vs. Exec
## Built-in vs. exec
Boundary comes with built-in wrappers for popular layer 7 connection protocols,
such as:
@@ -195,7 +195,7 @@ correct available binary (as WSL must use `.exe` when invoking Windows binaries)
$ boundary connect ssh -style putty -exec putty.exe -target-id ttcp_1234567890
```
## Connect using Desktop Client
## Connect using the desktop client
While using the desktop client, choose the target and connect to retrieve local
proxy details.
@@ -213,7 +213,7 @@ proxy details.
/>
</video>
## Next Steps
## Next steps
See our [basic administration
workflows](/boundary/tutorials/oss-administration)
@@ -1,10 +1,10 @@
---
layout: docs
page_title: What is Dev Mode?
description: Getting started with Boundary OSS in Dev mode
page_title: What is dev mode?
description: Getting started with Boundary OSS in dev mode
---
# What is Dev Mode?
# What is dev mode?
Dev mode is a method for getting started with Boundary quickly for testing and
learning purposes. As the name implies, dev mode is not a production
@@ -2,7 +2,7 @@
layout: docs
page_title: Run and log in to Boundary
description: |-
How to run Boundary services in dev mode and login for the first time.
How to run Boundary services in dev mode and log in for the first time.
---
# Run and log in to Boundary
@@ -114,7 +114,7 @@ the Boundary server does not use TLS in development mode.
</Tabs>
## Next Steps
## Next steps
See [connecting to your first
target](/boundary/docs/oss/installing/connect-to-dev-target) for how to use Boundary to