Obvious copy-paste issue (#488)

Configuration Javadoc (hence documentation) was totally off,
obvious copy paste issue, most probably when doco was modded
to support markdown generation.

No issue needed, as this fixes javadoc only (and generated
page).

maven-resolver-connector-basic/src/main/java/org/eclipse/aether/connector/basic/BasicRepositoryConnectorConfigurationKeys.java

@@ -50,8 +50,7 @@ private BasicRepositoryConnectorConfigurationKeys() {}
     public static final boolean DEFAULT_PERSISTED_CHECKSUMS = true;
 
     /**
-     * Flag indicating whether checksums which are retrieved during checksum validation should be persisted in the
-     * local repository next to the file they provide the checksum for.
+     * Number of threads in basic connector for uploading/downloading.
      *
      * @since 0.9.0.M4
      * @configurationSource {@link RepositorySystemSession#getConfigProperties()}

src/site/markdown/configuration.md

@@ -38,7 +38,7 @@ under the License.
 | 11. | `"aether.connector.basic.parallelPut"` | `Boolean` | Enables or disables parallel PUT processing (parallel deploys) on basic connector globally or per remote repository. When disabled, connector behaves exactly as in Maven 3.8.x did: GETs are parallel while PUTs are sequential. |  `true`  | 1.9.5 |  Yes  | Session Configuration |
 | 12. | `"aether.connector.basic.persistedChecksums"` | `Boolean` | Flag indicating whether checksums which are retrieved during checksum validation should be persisted in the local repository next to the file they provide the checksum for. |  `true`  | 0.9.0.M4 |  No  | Session Configuration |
 | 13. | `"aether.connector.basic.smartChecksums"` | `Boolean` | Flag indicating that instead of comparing the external checksum fetched from the remote repo with the calculated one, it should try to extract the reference checksum from the actual artifact response headers This only works for HTTP transports. |  `true`  | 0.9.0.M3 |  No  | Session Configuration |
-| 14. | `"aether.connector.basic.threads"` | `Integer` | Flag indicating whether checksums which are retrieved during checksum validation should be persisted in the local repository next to the file they provide the checksum for. |  `5`  | 0.9.0.M4 |  No  | Session Configuration |
+| 14. | `"aether.connector.basic.threads"` | `Integer` | Number of threads in basic connector for uploading/downloading. |  `5`  | 0.9.0.M4 |  No  | Session Configuration |
 | 15. | `"aether.dependencyCollector.bf.skipper"` | `Boolean` | The key in the repository session's  used to store a  flag controlling the resolver's skip mode. |  `true`  | 1.8.0 |  No  | Session Configuration |
 | 16. | `"aether.dependencyCollector.bf.threads"` | `Integer` | The count of threads to be used when collecting POMs in parallel. |  `5`  | 1.9.0 |  No  | Session Configuration |
 | 17. | `"aether.dependencyCollector.impl"` | `String` | The name of the dependency collector implementation to use: depth-first (original) named "df", and breadth-first (new in 1.8.0) named "bf". Both collectors produce equivalent results, but they may differ performance wise, depending on project being applied to. Our experience shows that existing "df" is well suited for smaller to medium size projects, while "bf" may perform better on huge projects with many dependencies. Experiment (and come back to us!) to figure out which one suits you the better. |  `"bf"`  | 1.8.0 |  No  | Session Configuration |