docs: Call "arrays" "lists"

We were flip-flopping between the two terms, so we now use one. We
still mention "array" in the chapter, and it's still `read --array`,
though.

Fixes #5846.

[ci skip]
This commit is contained in:
Fabian Homborg
2019-05-05 14:01:07 +02:00
parent d83636f70e
commit 8d9782301e
8 changed files with 37 additions and 37 deletions

View File

@@ -43,7 +43,7 @@ The following options are available:
- ``-x`` or ``--export`` exports the variables to child processes.
- ``-a`` or ``--array`` stores the result as an array in a single variable.
- ``-a`` or ``--array`` stores the result as a list in a single variable.
- ``-z`` or ``--null`` marks the end of the line with the NUL character, instead of newline. This also
disables interactive mode.
@@ -62,7 +62,7 @@ If no variable names are provided, ``read`` enters a special case that simply pr
When running in this mode, ``read`` does not split the input in any way and text is redirected to standard output without any further processing or manipulation.
If ``-a`` or ``--array`` is provided, only one variable name is allowed and the tokens are stored as an array in this variable.
If ``-a`` or ``--array`` is provided, only one variable name is allowed and the tokens are stored as a list in this variable.
See the documentation for ``set`` for more details on the scoping rules for variables.