Polishing.

Fix reference in javadoc

Author: christophstrobl

spring-data-jpa/src/main/java/org/springframework/data/jpa/repository/query/QueryEnhancer.java

@@ -82,7 +82,7 @@ public interface QueryEnhancer {
 	 * @param sort the sort specification to apply.
 	 * @param alias the alias to be used in the order by clause. May be {@literal null} or empty.
 	 * @return the modified query string.
-	 * @deprecated since 3.5, use {@link #rewrite(Sort, ReturnedType)} instead.
+	 * @deprecated since 3.5, use {@link #rewrite(QueryRewriteInformation)} instead.
 	 */
 	@Deprecated(since = "3.5", forRemoval = true)
 	String applySorting(Sort sort, @Nullable String alias);

src/main/antora/modules/ROOT/pages/repositories/projections.adoc

@@ -68,7 +68,7 @@ This query gets rewritten to `SELECT new UserDto(u.firstname, u.lastname) FROM U
 
 [WARNING]
 ====
-JPQL constructor expressions must not contain aliases for selected columns.
+JPQL constructor expressions must not contain aliases for selected columns and query rewriting will not remove them for you.
 While `SELECT u as user, count(u.roles) as roleCount FROM USER u …` is a valid query for interface-based projections that rely on column names from the returned `Tuple`, the same construct is invalid when requesting a DTO where it needs to be `SELECT u, count(u.roles) FROM USER u …`. +
 Some persistence providers may be lenient about this, others not.
 ====