Clarify how to find out the correct BUNDLE_ env var name

Author: eregon

README.md

@@ -167,7 +167,7 @@ as shown in the [example](#matrix-of-gemfiles).
 When using `bundler-cache: true` you might notice there is no good place to run `bundle config ...` commands.
 These can be replaced by `BUNDLE_*` environment variables, which are also faster.
 They should be set the `env` at the job level as shown in the [example](#matrix-of-gemfiles).
-See the [Bundler docs](https://bundler.io/man/bundle-config.1.html) or look at `.bundle/config` locally for the environment variable names,
+To find the correct the environment variable name, see the [Bundler docs](https://bundler.io/man/bundle-config.1.html) or look at `.bundle/config` after running `bundle config --local KEY VALUE` locally.
 
 To perform caching, this action will use `bundle config --local path $PWD/vendor/bundle`.  
 Therefore, the Bundler `path` should not be changed in your workflow for the cache to work (no `bundle config path`).