Docs: standardize between list and array as array

When arrays were added they were called arrays. Because the are
implemented with Python lists, that language started leaking into
talking about Meson types. This is confusing. I've attempted, as much as
possible, to move to using one name, array. I picked array because 1)
It's the original name used, and 2) what Meson has are more properly
arrays as they have a fixed length, while a critical property of lists
are the ability to link and unlink them.

There are a couple of places where the list language has leaked into the
names of keyword arguments. I have not made any attempt to change those,
I don't know if it's that useful or not.

1 files changed, 3 insertions, 3 deletions

diff --git a/docs/yaml/functions/executable.yaml b/docs/yaml/functions/executable.yaml
index df71b79fa..1e463edf0 100644
--- a/docs/yaml/functions/executable.yaml
+++ b/docs/yaml/functions/executable.yaml
@@ -4,9 +4,9 @@ description: |
   Creates a new executable. The first argument specifies its name and
   the remaining positional arguments define the input files to use.
 
-  The lists for the kwargs (such as `sources`, `objects`, and `dependencies`) are
-  always flattened, which means you can freely nest and add lists while
-  creating the final list.
+  The arrays for the kwargs (such as `sources`, `objects`, and `dependencies`) are
+  always flattened, which means you can freely nest and add arrays while
+  creating the final array.
 
   The returned object also has methods that are documented in [[@exe]].