doc: minor cleanup

Author: kwin

src/site/markdown/local-repository.md

@@ -192,12 +192,12 @@ For details see [Named Locks module](maven-resolver-named-locks/).
 
 ## Error Handling and Caching
 
-By default each artifact which cannot be resolved leads to an error either classified as 
+Each artifact/metadata which cannot be resolved leads to an error either classified as 
 
 1. *not found* error or
 2. (any) *other* error (for authentication issues, timeouts etc.)
 
-The caching behavior for both types can be be configured programmatically via `org.eclipse.aether.DefaultRepositorySystemSession.setResolutionErrorPolicy(...)`.
+The caching behavior for both error types can be be configured programmatically via `org.eclipse.aether.DefaultRepositorySystemSession.setResolutionErrorPolicy(...)`.
 
 In case caching is enabled for any of the two classifications a Java Properties file is created/updated (with the same filename as the cached artifact in the success case would get but with the additional suffix `.lastUpdated`) in the local repository. Within that file the key `<canonical-remote-url>.error` is updated/added. Its value either contains the error message (for type 2 resolver errors) or is empty (for type 1 resolver errors).