fix instances of bugprone-argument-comment

This new clang-tidy check complains when param names /*in_comments=*/
don't match up with the actual parameter name they're being passed to.
Sometimes this is benign, other times, actual bugs are found.

Bug: 1136209
Change-Id: Ic61630a22fda8a25377fbe2c9dd9818c1c5ec72f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2458849Reviewed-by: Marc Treib <treib@chromium.org>
Commit-Queue: George Burgess <gbiv@chromium.org>
Cr-Commit-Position: refs/heads/master@{#815699}

chrome/browser/sync/test/integration/two_client_custom_passphrase_sync_test.cc

@@ -62,13 +62,14 @@ class TwoClientCustomPassphraseSyncTestScryptEnabledInPreTest
   TwoClientCustomPassphraseSyncTestScryptEnabledInPreTest() {
     if (content::IsPreTest()) {
       override_features_.InitWithFeatures(
-          /*enable_features=*/{switches::kSyncUseScryptForNewCustomPassphrases},
-          /*disable_features=*/{
+          /*enabled_features=*/{switches::
+                                    kSyncUseScryptForNewCustomPassphrases},
+          /*disabled_features=*/{
               switches::kSyncForceDisableScryptForCustomPassphrase});
     } else {
       override_features_.InitWithFeatures(
-          /*enable_features=*/{},
-          /*disable_features=*/{
+          /*enabled_features=*/{},
+          /*disabled_features=*/{
               switches::kSyncUseScryptForNewCustomPassphrases,
               switches::kSyncForceDisableScryptForCustomPassphrase});
     }