From b8eb846075b2a9e93d5dc98ccb4c2fcab1790dd9 Mon Sep 17 00:00:00 2001
From: "Eric L. Barnes" <eric@ericlbarnes.com>
Date: Thu, 9 Nov 2017 22:50:01 -0500
Subject: [PATCH] Change the config.js to tailwind.js tht is recommended in
 step 3.

---
 docs/source/docs/installation.blade.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/source/docs/installation.blade.md b/docs/source/docs/installation.blade.md
index 2ea7b40a4f96..7d56f5393f50 100644
--- a/docs/source/docs/installation.blade.md
+++ b/docs/source/docs/installation.blade.md
@@ -110,7 +110,7 @@ To avoid specificity issues, we highly recommend structuring your main styleshee
 For simple projects or just giving Tailwind a spin, you can use the Tailwind CLI tool to process your CSS:
 
 <div class="bg-smoke-lighter font-mono text-sm p-4">
-  <div class="text-purple-dark">./node_modules/.bin/tailwind build <span class="text-blue-dark">styles.css</span> <span class="text-smoke-darker">[-c ./config.js] [-o ./output.css]</span></div>
+  <div class="text-purple-dark">./node_modules/.bin/tailwind build <span class="text-blue-dark">styles.css</span> <span class="text-smoke-darker">[-c ./tailwind.js] [-o ./output.css]</span></div>
 </div>
 
 #### Using Tailwind with PostCSS