From 2dba9b180b778733ae9f765e283b96b189072e9d Mon Sep 17 00:00:00 2001 From: Sami Rageb Date: Thu, 26 May 2016 20:14:59 -0500 Subject: [PATCH] Fixed & clarified grammar around HCL & JSON - Fixed the statement that HCL is JSON compatible, it's vice versa - Added that HCL is a superset of JSON to eliminate any lingering confusion --- website/source/intro/getting-started/deploy.html.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/source/intro/getting-started/deploy.html.md b/website/source/intro/getting-started/deploy.html.md index 044a257ec..6e19b25f5 100644 --- a/website/source/intro/getting-started/deploy.html.md +++ b/website/source/intro/getting-started/deploy.html.md @@ -19,8 +19,8 @@ seal/unseal process, and scaling Vault. ## Configuring Vault Vault is configured using [HCL](https://github.com/hashicorp/hcl) files. -As a reminder, these files are also JSON-compatible. The configuration -file for Vault is relatively simple. An example is shown below: +As a reminder, JSON files are also fully HCL-compatible; HCL is a superset of JSON. +The configuration file for Vault is relatively simple. An example is shown below: ```javascript backend "consul" {