From 1fd1cdf1d5e4b02506f4c9a58cf3661e6a95c44d Mon Sep 17 00:00:00 2001 From: Andreas Deininger Date: Sun, 24 Sep 2023 21:15:01 +0200 Subject: [PATCH] Fix typo --- content/documentation/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/documentation/troubleshooting.md b/content/documentation/troubleshooting.md index 48a316ea..6add1f4c 100644 --- a/content/documentation/troubleshooting.md +++ b/content/documentation/troubleshooting.md @@ -21,7 +21,7 @@ If executing `buffalo --help` or any other command from the terminal takes longe {{< faq "Can't find `buffalo` binary." "binary-not-found">}} -If you can't find the `buffalo` binary after a successful installation, this is problably caused because `$GOPATH/bin`, or `%GOPATH\bin` (Windows), isn't in your `$PATH` variable. When a Go binary is installed it is placed in `$GOPATH/bin`. Adding this to your global `$PATH` will allow you to find **any** Go binary everywhere in your system. See [golang.org/doc/code.html#GOPATH](https://golang.org/doc/code.html#GOPATH) for more details. +If you can't find the `buffalo` binary after a successful installation, this is probably caused because `$GOPATH/bin`, or `%GOPATH\bin` (Windows), isn't in your `$PATH` variable. When a Go binary is installed it is placed in `$GOPATH/bin`. Adding this to your global `$PATH` will allow you to find **any** Go binary everywhere in your system. See [golang.org/doc/code.html#GOPATH](https://golang.org/doc/code.html#GOPATH) for more details. {{< /faq >}} {{< faq "`buffalo new` fails to generate a complete project." "failed-to-gen">}}