Fix use of 'recipe'

kgryte · kgryte · commit 27f68f2b32c0 · 2018-01-11T00:51:09.000-08:00
diff --git a/tools/make/lib/benchmark/README.md b/tools/make/lib/benchmark/README.md
@@ -1,12 +1,12 @@
 # Benchmark
 
-> Benchmark recipes.
+> Benchmark commands.
 
 <!-- Section to include introductory text. Make sure to keep an empty line after the intro `section` element and another before the `/section` close. -->
 
 <section class="intro">
 
-This directory contains [`make`][make] recipes for running language benchmarks.
+This directory contains [`make`][make] rules for running language benchmarks.
 
 </section>
 
@@ -34,11 +34,11 @@ Runs benchmarks.
 $ make benchmark
 ```
 
-The recipe supports the following environment variables:
+The command supports the following environment variables:
 
 -   **BENCHMARKS_FILTER**: file path pattern; e.g., `.*/blas/base/dasum/.*`.
 
-This recipe is an **alias** for `benchmark-javascript`, which is documented below.
+This command is an **alias** for `benchmark-javascript`, which is documented below.
 
 
 #### benchmark-lang
@@ -51,15 +51,15 @@ Runs cross-language benchmarks.
 $ make benchmark-lang
 ```
 
-The recipe supports the environment variables supported by each language-specific (`benchmark-<lang>`) recipe documented below.
+The command supports the environment variables supported by each language-specific (`benchmark-<lang>`) command documented below.
 
-This recipe is useful when wanting to glob for benchmark files, irrespective of language, for a particular package in order to compare cross-language performance. 
+This command is useful when wanting to glob for benchmark files, irrespective of language, for a particular package in order to compare cross-language performance. 
 
 * * *
 
 ### C
 
-> **Note**: C benchmark recipes delegate to local Makefiles which are responsible for actually compiling and running the respective benchmarks.
+> **Note**: C benchmark commands delegate to local Makefiles which are responsible for actually compiling and running the respective benchmarks.
 
 #### benchmark-c
 
@@ -71,14 +71,14 @@ Runs C benchmarks.
 $ make benchmark-c
 ```
 
-The recipe supports the following environment variables:
+The command supports the following environment variables:
 
 -   **BENCHMARKS_FILTER**: file path pattern; e.g., `.*/math/base/special/abs/.*`.
 -   **BLAS**: BLAS library name; e.g., `openblas`.
 -   **BLAS_DIR**: BLAS directory.
 -   **C_COMPILER**: C compiler; e.g., `gcc`.
 
-This recipe is useful when wanting to glob for C benchmark files (e.g., run all C benchmarks for a particular package).
+This command is useful when wanting to glob for C benchmark files (e.g., run all C benchmarks for a particular package).
 
 #### benchmark-c-files
 
@@ -90,20 +90,20 @@ Runs a specified list of C benchmark files.
 $ make benchmark-c-files FILES='/foo/benchmark.c /bar/benchmark.c'
 ```
 
-The recipe supports the following environment variables:
+The command supports the following environment variables:
 
 -   **FILES**: list of C benchmark files.
 -   **BLAS**: BLAS library name; e.g., `openblas`.
 -   **BLAS_DIR**: BLAS directory.
 -   **C_COMPILER**: C compiler; e.g., `gcc`.
 
-This recipe is useful when wanting to run a list of C benchmark files generated by some other command (e.g., a filtered list of changed C benchmark files obtained via `git diff`).
+This command is useful when wanting to run a list of C benchmark files generated by some other command (e.g., a filtered list of changed C benchmark files obtained via `git diff`).
 
 * * *
 
 ### C++
 
-> **Note**: C++ benchmark recipes delegate to local Makefiles which are responsible for actually compiling and running the respective benchmarks.
+> **Note**: C++ benchmark commands delegate to local Makefiles which are responsible for actually compiling and running the respective benchmarks.
 
 #### benchmark-cpp
 
@@ -115,12 +115,12 @@ Runs C++ benchmarks.
 $ make benchmark-cpp
 ```
 
-The recipe supports the following environment variables:
+The command supports the following environment variables:
 
 -   **BENCHMARKS_FILTER**: file path pattern; e.g., `.*/math/base/special/beta/.*`.
 -   **CXX_COMPILER**: C++ compiler; e.g., `g++`.
 
-This recipe is useful when wanting to glob for C++ benchmark files (e.g., run all C++ benchmarks for a particular package).
+This command is useful when wanting to glob for C++ benchmark files (e.g., run all C++ benchmarks for a particular package).
 
 #### benchmark-cpp-files
 
@@ -132,18 +132,18 @@ Runs a specified list of C++ benchmark files.
 $ make benchmark-cpp-files FILES='/foo/benchmark.cpp /bar/benchmark.cpp'
 ```
 
-The recipe supports the following environment variables:
+The command supports the following environment variables:
 
 -   **FILES**: list of C++ benchmark files.
 -   **CXX_COMPILER**: C++ compiler; e.g., `g++`.
 
-This recipe is useful when wanting to run a list of C++ benchmark files generated by some other command (e.g., a filtered list of changed C++ benchmark files obtained via `git diff`).
+This command is useful when wanting to run a list of C++ benchmark files generated by some other command (e.g., a filtered list of changed C++ benchmark files obtained via `git diff`).
 
 * * *
 
 ### Fortran
 
-> **Note**: Fortran benchmark recipes delegate to local Makefiles which are responsible for actually compiling and running the respective benchmarks.
+> **Note**: Fortran benchmark commands delegate to local Makefiles which are responsible for actually compiling and running the respective benchmarks.
 
 #### benchmark-fortran
 
@@ -155,12 +155,12 @@ Runs Fortran benchmarks.
 $ make benchmark-fortran
 ```
 
-The recipe supports the following environment variables:
+The command supports the following environment variables:
 
 -   **BENCHMARKS_FILTER**: file path pattern; e.g., `.*/blas/base/daxpy/.*`.
 -   **FORTRAN_COMPILER**: Fortran compiler; e.g., `gfortran`.
 
-This recipe is useful when wanting to glob for Fortran benchmark files (e.g., run all Fortran benchmarks for a particular package).
+This command is useful when wanting to glob for Fortran benchmark files (e.g., run all Fortran benchmarks for a particular package).
 
 #### benchmark-fortran-files
 
@@ -172,12 +172,12 @@ Runs a specified list of Fortran benchmark files.
 $ make benchmark-fortran-files FILES='/foo/benchmark.f /bar/benchmark.f'
 ```
 
-The recipe supports the following environment variables:
+The command supports the following environment variables:
 
 -   **FILES**: list of Fortran benchmark files.
 -   **FORTRAN_COMPILER**: Fortran compiler; e.g., `gfortran`.
 
-This recipe is useful when wanting to run a list of Fortran benchmark files generated by some other command (e.g., a filtered list of changed Fortran benchmark files obtained via `git diff`).
+This command is useful when wanting to run a list of Fortran benchmark files generated by some other command (e.g., a filtered list of changed Fortran benchmark files obtained via `git diff`).
 
 * * *
 
@@ -193,11 +193,11 @@ Runs JavaScript benchmarks.
 $ make benchmark-javascript
 ```
 
-The recipe supports the following environment variables:
+The command supports the following environment variables:
 
 -   **BENCHMARKS_FILTER**: file path pattern; e.g., `.*/utils/group-by/.*`.
 
-This recipe is useful when wanting to glob for JavaScript benchmark files (e.g., run all JavaScript benchmarks for a particular package).
+This command is useful when wanting to glob for JavaScript benchmark files (e.g., run all JavaScript benchmarks for a particular package).
 
 #### benchmark-javascript-files
 
@@ -209,11 +209,11 @@ Runs a specified list of JavaScript benchmark files.
 $ make benchmark-javascript-files FILES='/foo/benchmark.js /bar/benchmark.js'
 ```
 
-The recipe supports the following environment variables:
+The command supports the following environment variables:
 
 -   **FILES**: list of JavaScript benchmark files.
 
-This recipe is useful when wanting to run a list of JavaScript benchmark files generated by some other command (e.g., a filtered list of changed JavaScript benchmark files obtained via `git diff`).
+This command is useful when wanting to run a list of JavaScript benchmark files generated by some other command (e.g., a filtered list of changed JavaScript benchmark files obtained via `git diff`).
 
 * * *
 
@@ -229,11 +229,11 @@ Runs Julia benchmarks.
 $ make benchmark-julia
 ```
 
-The recipe supports the following environment variables:
+The command supports the following environment variables:
 
 -   **BENCHMARKS_FILTER**: file path pattern; e.g., `.*/math/base/special/erf/.*`.
 
-This recipe is useful when wanting to glob for Julia benchmark files (e.g., run all Julia benchmarks for a particular package).
+This command is useful when wanting to glob for Julia benchmark files (e.g., run all Julia benchmarks for a particular package).
 
 #### benchmark-julia-files
 
@@ -245,11 +245,11 @@ Runs a specified list of Julia benchmark files.
 $ make benchmark-julia-files FILES='/foo/benchmark.jl /bar/benchmark.jl'
 ```
 
-The recipe supports the following environment variables:
+The command supports the following environment variables:
 
 -   **FILES**: list of Julia benchmark files.
 
-This recipe is useful when wanting to run a list of Julia benchmark files generated by some other command (e.g., a filtered list of changed Julia benchmark files obtained via `git diff`).
+This command is useful when wanting to run a list of Julia benchmark files generated by some other command (e.g., a filtered list of changed Julia benchmark files obtained via `git diff`).
 
 * * *
 
@@ -265,11 +265,11 @@ Runs Python benchmarks.
 $ make benchmark-python
 ```
 
-The recipe supports the following environment variables:
+The command supports the following environment variables:
 
 -   **BENCHMARKS_FILTER**: file path pattern; e.g., `.*/math/base/special/digamma/.*`.
 
-This recipe is useful when wanting to glob for Python benchmark files (e.g., run all Python benchmarks for a particular package).
+This command is useful when wanting to glob for Python benchmark files (e.g., run all Python benchmarks for a particular package).
 
 #### benchmark-python-files
 
@@ -281,11 +281,11 @@ Runs a specified list of Python benchmark files.
 $ make benchmark-python-files FILES='/foo/benchmark.py /bar/benchmark.py'
 ```
 
-The recipe supports the following environment variables:
+The command supports the following environment variables:
 
 -   **FILES**: list of Python benchmark files.
 
-This recipe is useful when wanting to run a list of Python benchmark files generated by some other command (e.g., a filtered list of changed Python benchmark files obtained via `git diff`).
+This command is useful when wanting to run a list of Python benchmark files generated by some other command (e.g., a filtered list of changed Python benchmark files obtained via `git diff`).
 
 * * *
 
@@ -301,11 +301,11 @@ Runs R benchmarks.
 $ make benchmark-r
 ```
 
-The recipe supports the following environment variables:
+The command supports the following environment variables:
 
 -   **BENCHMARKS_FILTER**: file path pattern; e.g., `.*/math/base/special/expm1/.*`.
 
-This recipe is useful when wanting to glob for R benchmark files (e.g., run all R benchmarks for a particular package).
+This command is useful when wanting to glob for R benchmark files (e.g., run all R benchmarks for a particular package).
 
 #### benchmark-r-files
 
@@ -317,11 +317,11 @@ Runs a specified list of R benchmark files.
 $ make benchmark-r-files FILES='/foo/benchmark.R /bar/benchmark.R'
 ```
 
-The recipe supports the following environment variables:
+The command supports the following environment variables:
 
 -   **FILES**: list of R benchmark files.
 
-This recipe is useful when wanting to run a list of R benchmark files generated by some other command (e.g., a filtered list of changed R benchmark files obtained via `git diff`).
+This command is useful when wanting to run a list of R benchmark files generated by some other command (e.g., a filtered list of changed R benchmark files obtained via `git diff`).
 
 </section>
 
