From 93d38ff2d2153197819747ba1273c0b05c9d4914 Mon Sep 17 00:00:00 2001
From: Pam Selle <204372+pselle@users.noreply.github.com>
Date: Thu, 1 Oct 2020 13:16:15 -0400
Subject: [PATCH] Update intro to code blocks

---
 website/docs/configuration/variables.html.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/docs/configuration/variables.html.md b/website/docs/configuration/variables.html.md
index a65806717..0829ec460 100644
--- a/website/docs/configuration/variables.html.md
+++ b/website/docs/configuration/variables.html.md
@@ -220,7 +220,7 @@ Sensitive values are still recorded in the [state](/docs/state/index.html), and
 
 A provider can define [an attribute as sensitive](/docs/extend/best-practices/sensitive-state.html#using-the-sensitive-flag), which prevents the value of that attribute from being displayed in logs or regular output. The `sensitive` argument on variables allows users to replicate this behavior for values in their configuration, by defining a variable as `sensitive`.
 
-Once you have defined a sensitive variable, using it throughout your configuration will obfuscate the value from display in output:
+Define a variable as sensitive by setting the `sensitive` argument to `true`:
 
 ```
 variable "user_information" {
@@ -237,7 +237,7 @@ resource "some_resource" "a" {
 }
 ```
 
-Running `terraform apply`:
+Using this variable throughout your configuration will obfuscate the value from display in `plan` or `apply` output:
 
 ```
 Terraform will perform the following actions: