Fix malformed list in "Using Method Parameters" documentation

Marcono1234 · jzheaux · commit a9aefafb7674 · 2024-07-01T15:18:17.000-06:00
diff --git a/docs/modules/ROOT/pages/servlet/authorization/method-security.adoc b/docs/modules/ROOT/pages/servlet/authorization/method-security.adoc
@@ -1804,7 +1804,7 @@ The intention of this expression is to require that the current `Authentication`
 +
 Behind the scenes, this is implemented by using `AnnotationParameterNameDiscoverer`, which you can customize to support the value attribute of any specified annotation.
 
-* If xref:servlet/integrations/data.adoc[Spring Data's] `@Param` annotation is present on at least one parameter for the method, the value is used.
+2. If xref:servlet/integrations/data.adoc[Spring Data's] `@Param` annotation is present on at least one parameter for the method, the value is used.
 The following example uses the `@Param` annotation:
 +
 [tabs]
@@ -1838,10 +1838,10 @@ The intention of this expression is to require that `name` be equal to `Authenti
 +
 Behind the scenes, this is implemented by using `AnnotationParameterNameDiscoverer`, which you can customize to support the value attribute of any specified annotation.
 
-* If you compile your code with the `-parameters` argument, the standard JDK reflection API is used to discover the parameter names.
+3. If you compile your code with the `-parameters` argument, the standard JDK reflection API is used to discover the parameter names.
 This works on both classes and interfaces.
 
-* Finally, if you compile your code with debug symbols, the parameter names are discovered by using the debug symbols.
+4. Finally, if you compile your code with debug symbols, the parameter names are discovered by using the debug symbols.
 This does not work for interfaces, since they do not have debug information about the parameter names.
 For interfaces, either annotations or the `-parameters` approach must be used.
 

Original file line number	Diff line number	Diff line change
@@ -1804,7 +1804,7 @@ The intention of this expression is to require that the current `Authentication`
`1804`	`1804`	`+`
`1805`	`1805`	Behind the scenes, this is implemented by using `AnnotationParameterNameDiscoverer`, which you can customize to support the value attribute of any specified annotation.
`1806`	`1806`
`1807`		-* If xref:servlet/integrations/data.adoc[Spring Data's] `@Param` annotation is present on at least one parameter for the method, the value is used.
	`1807`	+2. If xref:servlet/integrations/data.adoc[Spring Data's] `@Param` annotation is present on at least one parameter for the method, the value is used.
`1808`	`1808`	The following example uses the `@Param` annotation:
`1809`	`1809`	`+`
`1810`	`1810`	`[tabs]`
@@ -1838,10 +1838,10 @@ The intention of this expression is to require that `name` be equal to `Authenti
`1838`	`1838`	`+`
`1839`	`1839`	Behind the scenes, this is implemented by using `AnnotationParameterNameDiscoverer`, which you can customize to support the value attribute of any specified annotation.
`1840`	`1840`
`1841`		-* If you compile your code with the `-parameters` argument, the standard JDK reflection API is used to discover the parameter names.
	`1841`	+3. If you compile your code with the `-parameters` argument, the standard JDK reflection API is used to discover the parameter names.
`1842`	`1842`	`This works on both classes and interfaces.`
`1843`	`1843`
`1844`		`-* Finally, if you compile your code with debug symbols, the parameter names are discovered by using the debug symbols.`
	`1844`	`+4. Finally, if you compile your code with debug symbols, the parameter names are discovered by using the debug symbols.`
`1845`	`1845`	`This does not work for interfaces, since they do not have debug information about the parameter names.`
`1846`	`1846`	For interfaces, either annotations or the `-parameters` approach must be used.
`1847`	`1847`