go with List rather than Iterable because Iterable is just a PITA to deal with

Author: gavinking

api/src/main/java/jakarta/data/repository/Delete.java

@@ -65,7 +65,7 @@
  * to be deleted is the primary entity type of the repository. The method return type must be {@code void}, {@code int},
  * or {@code long}. Every parameter of the annotated method must have exactly the same name (the parameter name in the
  * Java source, or a name assigned by {@link By @By}) as a persistent field or property of the entity class and be of
- * type {@code T}, {@code T[]}, or {@code Iterable<T>} where {@code T} is the type of the field or property. Parameters
+ * type {@code T}, {@code T[]}, or {@code List<T>} where {@code T} is the type of the field or property. Parameters
  * of type {@code Sort}, {@code Order}, {@code Limit}, and {@code PageRequest} are prohibited.
  * </p>
  * <p>For example, consider an interface representing a garage:</p>

api/src/main/java/jakarta/data/repository/Find.java

@@ -34,8 +34,8 @@
  * </p>
  * <ul>
  * <li>have exactly the name (the parameter name in the Java source, or a name assigned by {@link By @By}) as a
- *     persistent field or property of the entity class and be of type {@code T}, {@code T[]}, or {@code Iterable<T>}
- *     where {@code T} is the type of the field or property, or</li>
+ *     persistent field or property of the entity class and be of type {@code T}, {@code T[]}, or {@code List<T>} where
+ *     {@code T} is the type of the field or property, or</li>
  * <li>be of type {@link jakarta.data.Limit}, {@link jakarta.data.Sort}, {@link jakarta.data.Order}, or
  *     {@link jakarta.data.page.PageRequest}.</li>
  * </ul>

spec/src/main/asciidoc/repository.asciidoc

@@ -826,12 +826,12 @@ A _parameter-based automatic query method_ is an abstract method annotated with
 
 Each automatic query method must be assigned an entity type. The rules for inferring the entity type depend on the semantics of the automatic query annotation. Typically:
 
-- If the automatic query method returns an entity type, the method return type identifies the entity. For example, the return type might be `E`, `Optional<E>`, `Page<E>`, or `List<E>`, where `E` is an entity class. Then the automatic query method would be assigned the entity type `E`.
+- If the automatic query method returns an entity type, the method return type identifies the entity. For example, the return type might be `E`, `Optional<E>`, `E[]`, `Page<E>`, or `List<E>`, where `E` is an entity class. Then the automatic query method would be assigned the entity type `E`.
 - If the query does not return an entity type, the entity assigned to the automatic query method is the primary entity type of the repository.
 
 Jakarta Data infers a query based on the parameters of the method. Each parameter must either:
 
-- have exactly the same name as a persistent field or property of the entity class and be of type `T`, `T[]`, or `Iterable<T>` where `T` is the type of the field or property, or
+- have exactly the same name as a persistent field or property of the entity class and be of type `T`, `T[]`, or `List<T>` where `T` is the type of the field or property, or
 - be of type `Limit`, `Order`, `PageRequest`, or `Sort`.
 
 Parameter names map parameters to persistent fields. A repository with parameter-based automatic query methods must either: