From ade67e6bb5f29c9f5d03fad10b977f1d5bcb05d0 Mon Sep 17 00:00:00 2001
From: xuwhao <46437721+xuwhao@users.noreply.github.com>
Date: Wed, 28 Jul 2021 07:36:42 +0800
Subject: [PATCH] fixed typo: specifc -> specific, varibles -> variables,
 idomatic -> idiomatic. (#1421)

---
 .../docs/common-workflows/workflow-ssh-proxycommand.mdx       | 4 ++--
 website/content/docs/configuration/kms/aead.mdx               | 2 +-
 website/content/docs/configuration/kms/index.mdx              | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/content/docs/common-workflows/workflow-ssh-proxycommand.mdx b/website/content/docs/common-workflows/workflow-ssh-proxycommand.mdx
index 1de9e1de10..c9f9b1421c 100644
--- a/website/content/docs/common-workflows/workflow-ssh-proxycommand.mdx
+++ b/website/content/docs/common-workflows/workflow-ssh-proxycommand.mdx
@@ -7,7 +7,7 @@ description: How to manage SSH proxy configuration with Boundary
 # SSH ProxyCommand Workflow
 
 The most common pattern for using Boundary to SSH is with the built-in `boundary connect ssh` command. However,
-there are more idomatic approaches that can be employed to make Boundary transparent to users, and at the same
+there are more idiomatic approaches that can be employed to make Boundary transparent to users, and at the same
 time simplify common developer and operator workflows. Using `ProxyCommand` to execute a proxy when invoking the
 SSH client is a common practice. In this workflow, we'll cover configuring your SSH client to execute the
 `boundary` command, enabling a simplified SSH workflow that leverages Boundary's authenticated proxy for accessing
@@ -24,7 +24,7 @@ Host ttcp_*
 
 The `ProxyCommand` tells the SSH client to invoke `boundary connect`. We are passing the `-exec nc` flag to
 `boundary connect` to wrap [netcat](http://netcat.sourceforge.net/), and then pass the `boundary.ip` and `boundary.port`
-varibles as arguments to `nc`. This allows us to proxy our SSH connection through a local netcat tunnel that's
+variables as arguments to `nc`. This allows us to proxy our SSH connection through a local netcat tunnel that's
 managed as a Boundary session.
 
 When you run `ssh ttcp_1234567890` (example target ID), SSH will invoke `boundary connect`, and will tunnel the traffic through
diff --git a/website/content/docs/configuration/kms/aead.mdx b/website/content/docs/configuration/kms/aead.mdx
index 0a6d508e05..7be96f5ab3 100644
--- a/website/content/docs/configuration/kms/aead.mdx
+++ b/website/content/docs/configuration/kms/aead.mdx
@@ -2,7 +2,7 @@
 layout: docs
 page_title: AEAD - Configuration
 description: |-
-  The AEAD KMS configures AEAD-specifc parameters.
+  The AEAD KMS configures AEAD-specific parameters.
 ---
 
 ~> This is mostly used for `dev` workflows or testing. The key will be exposed
diff --git a/website/content/docs/configuration/kms/index.mdx b/website/content/docs/configuration/kms/index.mdx
index 41bdc63b2d..7c2b8cb9a3 100644
--- a/website/content/docs/configuration/kms/index.mdx
+++ b/website/content/docs/configuration/kms/index.mdx
@@ -2,7 +2,7 @@
 layout: docs
 page_title: KMS - Configuration
 description: |-
-  The KMS stanza configures KMS-specifc parameters.
+  The KMS stanza configures KMS-specific parameters.
 ---
 
 # `kms` Stanza