| commit | bd8f120e95faf7a03d1f0637bfb32856670a86d6 | [log] [tgz] |
|---|---|---|
| author | Curtis Belmonte <curtislb@google.com> | Tue Jul 28 20:12:46 2020 +0000 |
| committer | Curtis Belmonte <curtislb@google.com> | Tue Jul 28 20:12:49 2020 +0000 |
| tree | f80a39318ac81a15dc3786e74d7c6649a6742902 | |
| parent | ed7662f6f6ff1e00ba46a67058cadca3eeeed825 [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: I89dbc737c62a796d3622cf17437f9eac930c99b3
diff --git a/src/com/android/settings/password/ConfirmDeviceCredentialActivity.java b/src/com/android/settings/password/ConfirmDeviceCredentialActivity.java index 8476f92..fbc2c3c 100644 --- a/src/com/android/settings/password/ConfirmDeviceCredentialActivity.java +++ b/src/com/android/settings/password/ConfirmDeviceCredentialActivity.java
@@ -318,7 +318,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