Polishing

spring-web/src/main/java/org/springframework/http/converter/FormHttpMessageConverter.java

@@ -232,7 +232,8 @@ public class FormHttpMessageConverter implements HttpMessageConverter<MultiValue
 	}
 
 	/**
-	 * Return the {@link #setPartConverters configured} converters for MIME parts.
+	 * Return the {@linkplain #setPartConverters configured converters} for MIME
+	 * parts.
 	 * @since 5.3
 	 */
 	public List<HttpMessageConverter<?>> getPartConverters() {

spring-webmvc/src/main/java/org/springframework/web/servlet/mvc/method/annotation/ServletRequestMethodArgumentResolver.java

@@ -89,7 +89,7 @@ public class ServletRequestMethodArgumentResolver implements HandlerMethodArgume
 				MultipartRequest.class.isAssignableFrom(paramType) ||
 				HttpSession.class.isAssignableFrom(paramType) ||
 				(pushBuilder != null && pushBuilder.isAssignableFrom(paramType)) ||
-				(Principal.class.isAssignableFrom(paramType) && parameter.getParameterAnnotations().length == 0) ||
+				(Principal.class.isAssignableFrom(paramType) && !parameter.hasParameterAnnotations()) ||
 				InputStream.class.isAssignableFrom(paramType) ||
 				Reader.class.isAssignableFrom(paramType) ||
 				HttpMethod.class == paramType ||

src/docs/asciidoc/web/webflux.adoc

@@ -971,8 +971,8 @@ The following example shows how to do so for client-side requests:
 
 Logging libraries such as SLF4J and Log4J 2 provide asynchronous loggers that avoid
 blocking. While those have their own drawbacks such as potentially dropping messages
-that could not be queued for logging, they are the best available option currently
-or use in a reactive, non-blocking application.
+that could not be queued for logging, they are the best available options currently
+for use in a reactive, non-blocking application.