From 854e1bf096aa6dd2468e8c8005eb05a32f310be9 Mon Sep 17 00:00:00 2001
From: William Mortada <william@mortada.co.uk>
Date: Sun, 8 Oct 2017 10:10:49 +0100
Subject: [PATCH] Fix the test for checking your path

The command `which civibuild` returns nothing even if the path is set correctly.
---
 docs/tools/buildkit.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/tools/buildkit.md b/docs/tools/buildkit.md
index e4afcf4c..beb2988b 100644
--- a/docs/tools/buildkit.md
+++ b/docs/tools/buildkit.md
@@ -81,7 +81,7 @@ If you want to ensure that the buildkit CLI tools are always available, then:
 1. Determine the location of your shell configuration file. This is usually `~/.bashrc`, `~/.bash_profile`, or `~/.profile`.
 1. At the end of the file, add `export PATH="/path/to/buildkit/bin:$PATH"`.
 1. Close and reopen the terminal.
-1. Enter the command `which civibuild`. This should display a full-path. If nothing appears, then retry the steps.
+1. Enter the command `civibuild -v`. This should display a help screen for civibuild. If you get 'command not found', then check your path and retry the steps above.
 
 
 !!! note
-- 
GitLab