diff --git a/app/src/main/java/org/thoughtcrime/securesms/database/StorySendsDatabase.kt b/app/src/main/java/org/thoughtcrime/securesms/database/StorySendsDatabase.kt index 1b31682ee..6573da019 100644 --- a/app/src/main/java/org/thoughtcrime/securesms/database/StorySendsDatabase.kt +++ b/app/src/main/java/org/thoughtcrime/securesms/database/StorySendsDatabase.kt @@ -12,7 +12,7 @@ import org.thoughtcrime.securesms.recipients.RecipientId /** * Sending to a distribution list is a bit trickier. When we send to multiple distribution lists with overlapping membership, we want to * show them as distinct items on the sending side, but as a single item on the receiving side. Basically, if Alice has two lists and Bob - * is on both, Bob should always see a story for “Alice” and not know that Alice has him in multiple lists. And when Bob views the story, + * is on both, Bob should always see a story for "Alice" and not know that Alice has him in multiple lists. And when Bob views the story, * Alice should update the UI to show a view in each list. To do this, we need to: * 1. Only send a single copy of each story to a given recipient, while * 2. Knowing which people would have gotten duplicate copies. diff --git a/app/src/main/java/org/thoughtcrime/securesms/service/SmsListener.java b/app/src/main/java/org/thoughtcrime/securesms/service/SmsListener.java index 0a0a354ff..19b579287 100644 --- a/app/src/main/java/org/thoughtcrime/securesms/service/SmsListener.java +++ b/app/src/main/java/org/thoughtcrime/securesms/service/SmsListener.java @@ -49,7 +49,7 @@ public class SmsListener extends BroadcastReceiver { return message.getOriginatingAddress().length() < 7 && (messageBody.toUpperCase().startsWith("//ANDROID:") || // Sprint Visual Voicemail - messageBody.startsWith("//BREW:")); //BREW stands for “Binary Runtime Environment for Wireless" + messageBody.startsWith("//BREW:")); //BREW stands for "Binary Runtime Environment for Wireless" } private SmsMessage getSmsMessageFromIntent(Intent intent) { diff --git a/libsignal/service/src/main/java/org/whispersystems/signalservice/api/subscriptions/ActiveSubscription.java b/libsignal/service/src/main/java/org/whispersystems/signalservice/api/subscriptions/ActiveSubscription.java index dbc036a87..302129546 100644 --- a/libsignal/service/src/main/java/org/whispersystems/signalservice/api/subscriptions/ActiveSubscription.java +++ b/libsignal/service/src/main/java/org/whispersystems/signalservice/api/subscriptions/ActiveSubscription.java @@ -252,7 +252,7 @@ public final class ActiveSubscription { /** * Possible values are approved_by_network, declined_by_network, not_sent_to_network, and reversed_after_approval. * The value reversed_after_approval indicates the payment was blocked by Stripe after bank authorization, - * and may temporarily appear as “pending” on a cardholder’s statement. + * and may temporarily appear as "pending" on a cardholder's statement. *

* See: https://stripe.com/docs/api/charges/object#charge_object-outcome-network_status */ @@ -261,8 +261,8 @@ public final class ActiveSubscription { } /** - * An enumerated value providing a more detailed explanation of the outcome’s type. Charges blocked by Radar’s default block rule have the value - * highest_risk_level. Charges placed in review by Radar’s default review rule have the value elevated_risk_level. Charges authorized, blocked, or placed + * An enumerated value providing a more detailed explanation of the outcome's type. Charges blocked by Radar's default block rule have the value + * highest_risk_level. Charges placed in review by Radar's default review rule have the value elevated_risk_level. Charges authorized, blocked, or placed * in review by custom rules have the value rule. See understanding declines for more details. *

* See: https://stripe.com/docs/api/charges/object#charge_object-outcome-reason