From a943c943cf5f325076d333e296f225d69516884b Mon Sep 17 00:00:00 2001
From: Matthew Sanabria <24284972+sudomateo@users.noreply.github.com>
Date: Wed, 22 Jul 2020 11:05:15 -0400
Subject: [PATCH] Syntax updates

It's easier to read inline monospace characters than quoted characters,
especially when the content itself refers to a file or directory name.
---
 tools/terraform-bundle/README.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/tools/terraform-bundle/README.md b/tools/terraform-bundle/README.md
index 8af8f98f9..916b33c1d 100644
--- a/tools/terraform-bundle/README.md
+++ b/tools/terraform-bundle/README.md
@@ -123,8 +123,8 @@ distinguished from official release archives and from each other when multiple
 bundles contain the same core Terraform version.
 
 ## Custom Plugins
-To include custom plugins in the bundle file, create a local directory
-"./plugins" and put all the plugins you want to include there, under the
+To include custom plugins in the bundle file, create a local directory named
+`./plugins` and put all the plugins you want to include there, under the
 required [sub directory](#plugins-directory-layout). Optionally, you can use the
 `-plugin-dir` flag to specify a location where to find the plugins. To be
 recognized as a valid plugin, the file must have a name of the form
@@ -135,7 +135,7 @@ Typically this will be `linux` and `amd64`.
 ### Plugins Directory Layout
 To include custom plugins in the bundle file, you must specify a "source"
 attribute in the configuration and place the plugin in the appropriate
-subdirectory under "./plugins". The directory must have the following layout:
+subdirectory under `./plugins`. The directory must have the following layout:
 
 ```
 ./plugins/$SOURCEHOST/$SOURCENAMESPACE/$NAME/$VERSION/$OS_$ARCH/