From a6a8e8b33a259aabfe8478d2de74546112d78707 Mon Sep 17 00:00:00 2001
From: Jason O'Donnell <2160810+jasonodonnell@users.noreply.github.com>
Date: Wed, 26 Jun 2019 10:26:18 -0400
Subject: [PATCH] Remove old 0.6.0 note from vault doc

---
 vault/content.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/vault/content.md b/vault/content.md
index 641d6df1b..03ab0129b 100644
--- a/vault/content.md
+++ b/vault/content.md
@@ -20,7 +20,7 @@ The container exposes two optional `VOLUME`s:
 -	`/vault/logs`, to use for writing persistent audit logs. By default nothing is written here; the `file` audit backend must be enabled with a path under this directory.
 -	`/vault/file`, to use for writing persistent storage data when using the`file` data storage plugin. By default nothing is written here (a `dev` server uses an in-memory data store); the `file` data storage backend must be enabled in Vault's configuration before the container is started.
 
-The container has a Vault configuration directory set up at `/vault/config` and the server will load any HCL or JSON configuration files placed here by binding a volume or by composing a new image and adding files. Alternatively, configuration can be added by passing the configuration JSON via environment variable `VAULT_LOCAL_CONFIG`. Please note that due to a bug in the current release of Vault (0.6.0), you should *not* use the name `local.json` for any configuration file in this directory.
+The container has a Vault configuration directory set up at `/vault/config` and the server will load any HCL or JSON configuration files placed here by binding a volume or by composing a new image and adding files. Alternatively, configuration can be added by passing the configuration JSON via environment variable `VAULT_LOCAL_CONFIG`.
 
 ## Memory Locking and 'setcap'