| commit | 5cc1ba2f7f38653961d8c311c19a1f9135c74a59 | [log] [tgz] |
|---|---|---|
| author | Curtis Belmonte <curtislb@google.com> | Tue Jul 28 20:29:07 2020 +0000 |
| committer | Curtis Belmonte <curtislb@google.com> | Tue Jul 28 20:29:10 2020 +0000 |
| tree | 038a4cede155e473a3b067a505c1fec3d9fe9226 | |
| parent | 71bbcd26d5f772e747a7d62b92251b4161ef0504 [diff] |
Update language to comply with Android's inclusive language guidance See https://source.android.com/setup/contribute/respectful-code for reference Test: Presubmit Bug: 161896447 Change-Id: I51d34cee1a37ffc1f9dea47893d5749949887d91
diff --git a/tests/CarDeveloperOptions/src/com/android/car/developeroptions/password/ConfirmDeviceCredentialActivity.java b/tests/CarDeveloperOptions/src/com/android/car/developeroptions/password/ConfirmDeviceCredentialActivity.java index 12afab1..db0a08b 100644 --- a/tests/CarDeveloperOptions/src/com/android/car/developeroptions/password/ConfirmDeviceCredentialActivity.java +++ b/tests/CarDeveloperOptions/src/com/android/car/developeroptions/password/ConfirmDeviceCredentialActivity.java
@@ -315,7 +315,7 @@ boolean launched = false; // The only difference between CREDENTIAL_MANAGED and CREDENTIAL_NORMAL is that for // CREDENTIAL_MANAGED, we launch the real confirm credential activity with an explicit - // but dummy challenge value (0L). This will result in ConfirmLockPassword calling + // but fake challenge value (0L). This will result in ConfirmLockPassword calling // verifyTiedProfileChallenge() (if it's a profile with unified challenge), due to the // difference between ConfirmLockPassword.startVerifyPassword() and // ConfirmLockPassword.startCheckPassword(). Calling verifyTiedProfileChallenge() here is