"list" -> "array" in two places in README.md

trailofbits · Jul 31, 2024 · 353a816 · 353a816
1 parent 44ca079
commit 353a816
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/README.md b/README.md
@@ -62,7 +62,7 @@ Helpful [resources] for writing lints appear below.
 
 ### Workspace metadata
 
-A workspace can name the libraries it should be linted with in its `Cargo.toml` or `dylint.toml` file. Specifically, either file can contain a TOML list under `workspace.metadata.dylint.libraries`. Each list entry must have the form of a Cargo `git` or `path` dependency, with the following differences:
+A workspace can name the libraries it should be linted with in its `Cargo.toml` or `dylint.toml` file. Specifically, either file can contain a TOML array under `workspace.metadata.dylint.libraries`. Each array entry must have the form of a Cargo `git` or `path` dependency, with the following differences:
 
 - There is no leading package name, i.e., no `package =`.
 - `path` entries can contain [glob] patterns, e.g., `*`.

diff --git a/cargo-dylint/README.md b/cargo-dylint/README.md
@@ -62,7 +62,7 @@ Helpful [resources] for writing lints appear below.
 
 ### Workspace metadata
 
-A workspace can name the libraries it should be linted with in its `Cargo.toml` or `dylint.toml` file. Specifically, either file can contain a TOML list under `workspace.metadata.dylint.libraries`. Each list entry must have the form of a Cargo `git` or `path` dependency, with the following differences:
+A workspace can name the libraries it should be linted with in its `Cargo.toml` or `dylint.toml` file. Specifically, either file can contain a TOML array under `workspace.metadata.dylint.libraries`. Each array entry must have the form of a Cargo `git` or `path` dependency, with the following differences:
 
 - There is no leading package name, i.e., no `package =`.
 - `path` entries can contain [glob] patterns, e.g., `*`.

diff --git a/dylint/README.md b/dylint/README.md
@@ -62,7 +62,7 @@ Helpful [resources] for writing lints appear below.
 
 ### Workspace metadata
 
-A workspace can name the libraries it should be linted with in its `Cargo.toml` or `dylint.toml` file. Specifically, either file can contain a TOML list under `workspace.metadata.dylint.libraries`. Each list entry must have the form of a Cargo `git` or `path` dependency, with the following differences:
+A workspace can name the libraries it should be linted with in its `Cargo.toml` or `dylint.toml` file. Specifically, either file can contain a TOML array under `workspace.metadata.dylint.libraries`. Each array entry must have the form of a Cargo `git` or `path` dependency, with the following differences:
 
 - There is no leading package name, i.e., no `package =`.
 - `path` entries can contain [glob] patterns, e.g., `*`.