From 5c26e651e61d03d19909caf3df14738ddc55d6b9 Mon Sep 17 00:00:00 2001
From: Brian Cain <bcain@hashicorp.com>
Date: Thu, 26 Sep 2019 13:15:16 -0700
Subject: [PATCH] Move around example mention in docs

---
 website/source/docs/triggers/configuration.html.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/source/docs/triggers/configuration.html.md b/website/source/docs/triggers/configuration.html.md
index cef5435ac..baec4e22b 100644
--- a/website/source/docs/triggers/configuration.html.md
+++ b/website/source/docs/triggers/configuration.html.md
@@ -75,9 +75,9 @@ The trigger class takes various options.
   + `path`
 
     **Note:** The `run` option with `inline` is not entirely like a shell provisioner that runs bash.
-    It executes binaries on your machine rather than a bash script. If you wish you use
-    bash to pipe some text to a file in your `run` option with `inline`, wrap
-    your inline script with _`bash -c "<script goes here>"`_. For example:
+    It executes binaries on your machine rather than a bash script. For example:
+    If you wish you use bash to pipe some text to a file in your `run` option with `inline`, wrap
+    your inline script with _`bash -c "<script goes here>"`_.:
 
     ```ruby
     config.trigger.after :up do |trigger|