diff --git a/website/content/docs/getting-started/connect-to-target.mdx b/website/content/docs/getting-started/connect-to-target.mdx
index 2e74eed6e..18e605459 100644
--- a/website/content/docs/getting-started/connect-to-target.mdx
+++ b/website/content/docs/getting-started/connect-to-target.mdx
@@ -111,3 +111,8 @@ correct available binary, as WSL must use `.exe` when invoking Windows binaries:
 ```
 $ boundary connect ssh -style putty -exec putty.exe -target-id ttcp_1234567890
 ```
+
+## Next Steps
+
+See our [common workflows](/docs/common-workflows) for in depth discussion on managing scopes, targets, 
+identities, and sessions.
diff --git a/website/content/docs/getting-started/index.mdx b/website/content/docs/getting-started/index.mdx
index 0328a267b..4d1204a27 100644
--- a/website/content/docs/getting-started/index.mdx
+++ b/website/content/docs/getting-started/index.mdx
@@ -15,6 +15,7 @@ The examples in Getting Started all revolve around running in `dev mode`. There
 
 1. Docker is installed
 2. A route to download the [Postgres Docker image](https://hub.docker.com/_/postgres) is available or a local image cache is available
+3. A boundary binary in your $PATH
 
 ## What is Dev Mode?
 
diff --git a/website/content/docs/getting-started/run-and-login.mdx b/website/content/docs/getting-started/run-and-login.mdx
index e4f9a6748..f740b8051 100644
--- a/website/content/docs/getting-started/run-and-login.mdx
+++ b/website/content/docs/getting-started/run-and-login.mdx
@@ -49,3 +49,8 @@ provider "boundary" {
 
 Note in the example above we're setting `base_url` to `http` and not `https` as
 the Boundary server does not use TLS in development mode.
+
+## Next Steps
+
+See [connecting to your first target](/docs/getting-started/connect-to-target) for how
+to use Boundary to run your first SSH session.