Use standard "exception parameter" terminology (#902)

Co-authored-by: Werner Dietl <[email protected]>

docs/manual/advanced-features.tex

@@ -384,11 +384,11 @@
 locations.
 
 Variables defaulted to top include local variables, resource variables in the
-try-with-resources construct, variables in \<for> statements, and \<catch>
-arguments (known as exception parameters in the Java Language Specification).
+try-with-resources construct, and variables in \<for> statements.
 
-Exception parameters default to the top type because they might catch an
-exception thrown anywhere in the program.
+\item
+Exception parameters in catch clauses default to the top type because they
+might catch an exception thrown anywhere in the program.
 
 An alternate design for exception parameters would be to default exception
 parameters some other type T (instead of the top type); then the Checker

framework/src/main/java/org/checkerframework/common/basetype/messages.properties

@@ -31,7 +31,7 @@ type.invalid.super.wildcard=bounds must have the same annotations.%nextends boun
 cast.unsafe=cast from "%s" to "%s" cannot be statically verified
 invariant.cast.unsafe=cannot cast from "%s" to "%s"
 cast.unsafe.constructor.invocation=constructor invocation cast from "%s" to "%s" cannot be statically verified
-exception.parameter.invalid=invalid type in catch argument.%nfound   : %s%nrequired: %s
+exception.parameter.invalid=invalid type in exception parameter.%nfound   : %s%nrequired: %s
 throw.type.invalid=invalid type thrown.%nfound   : %s%nrequired: %s
 expression.unparsable.type.invalid=Expression invalid in dependent type annotation: %s
 explicit.annotation.ignored=The qualifier %s is ignored in favor of %s. Either delete %s or change it to %s.