nit on warning

Author: cbaker6

Sources/ParseSwift/Objects/ParseInstallation.swift

@@ -445,8 +445,8 @@ extension ParseInstallation {
      `isIgnoreCustomObjectIdConfig = false`. Setting
      `ParseConfiguration.allowCustomObjectId = true` and
      `isIgnoreCustomObjectIdConfig = true` means the client will generate `objectId`'s
-     and the server will generate an `objectId` only when the client does not provide one. This can lead
-     to collisions of `objectId`'s as the client and server `objectId`'s may be generated using
+     and the server will generate an `objectId` only when the client does not provide one. This can
+     increase the probability of colliiding `objectId`'s as the client and server `objectId`'s may be generated using
      different algorithms. This can also lead to overwriting of `ParseObject`'s by accident as the
      client-side checks are disabled. Developers are responsible for handling such cases.
     */
@@ -496,8 +496,8 @@ extension ParseInstallation {
      `isIgnoreCustomObjectIdConfig = false`. Setting
      `ParseConfiguration.allowCustomObjectId = true` and
      `isIgnoreCustomObjectIdConfig = true` means the client will generate `objectId`'s
-     and the server will generate an `objectId` only when the client does not provide one. This can lead
-     to collisions of `objectId`'s as the client and server `objectId`'s may be generated using
+     and the server will generate an `objectId` only when the client does not provide one. This can
+     increase the probability of colliiding `objectId`'s as the client and server `objectId`'s may be generated using
      different algorithms. This can also lead to overwriting of `ParseObject`'s by accident as the
      client-side checks are disabled. Developers are responsible for handling such cases.
     */
@@ -700,8 +700,8 @@ public extension Sequence where Element: ParseInstallation {
      `isIgnoreCustomObjectIdConfig = false`. Setting
      `ParseConfiguration.allowCustomObjectId = true` and
      `isIgnoreCustomObjectIdConfig = true` means the client will generate `objectId`'s
-     and the server will generate an `objectId` only when the client does not provide one. This can lead
-     to collisions of `objectId`'s as the client and server `objectId`'s may be generated using
+     and the server will generate an `objectId` only when the client does not provide one. This can
+     increase the probability of colliiding `objectId`'s as the client and server `objectId`'s may be generated using
      different algorithms. This can also lead to overwriting of `ParseObject`'s by accident as the
      client-side checks are disabled. Developers are responsible for handling such cases.
     */
@@ -801,8 +801,8 @@ public extension Sequence where Element: ParseInstallation {
      `isIgnoreCustomObjectIdConfig = false`. Setting
      `ParseConfiguration.allowCustomObjectId = true` and
      `isIgnoreCustomObjectIdConfig = true` means the client will generate `objectId`'s
-     and the server will generate an `objectId` only when the client does not provide one. This can lead
-     to collisions of `objectId`'s as the client and server `objectId`'s may be generated using
+     and the server will generate an `objectId` only when the client does not provide one. This can
+     increase the probability of colliiding `objectId`'s as the client and server `objectId`'s may be generated using
      different algorithms. This can also lead to overwriting of `ParseObject`'s by accident as the
      client-side checks are disabled. Developers are responsible for handling such cases.
     */

Sources/ParseSwift/Objects/ParseObject+combine.swift

@@ -105,8 +105,8 @@ public extension Sequence where Element: ParseObject {
      `isIgnoreCustomObjectIdConfig = false`. Setting
      `ParseConfiguration.allowCustomObjectId = true` and
      `isIgnoreCustomObjectIdConfig = true` means the client will generate `objectId`'s
-     and the server will generate an `objectId` only when the client does not provide one. This can lead
-     to collisions of `objectId`'s as the client and server `objectId`'s may be generated using
+     and the server will generate an `objectId` only when the client does not provide one. This can
+     increase the probability of colliiding `objectId`'s as the client and server `objectId`'s may be generated using
      different algorithms. This can also lead to overwriting of `ParseObject`'s by accident as the
      client-side checks are disabled. Developers are responsible for handling such cases.
     */

Sources/ParseSwift/Objects/ParseObject.swift

@@ -82,8 +82,8 @@ public extension Sequence where Element: ParseObject {
      `isIgnoreCustomObjectIdConfig = false`. Setting
      `ParseConfiguration.allowCustomObjectId = true` and
      `isIgnoreCustomObjectIdConfig = true` means the client will generate `objectId`'s
-     and the server will generate an `objectId` only when the client does not provide one. This can lead
-     to collisions of `objectId`'s as the client and server `objectId`'s may be generated using
+     and the server will generate an `objectId` only when the client does not provide one. This can
+     increase the probability of colliiding `objectId`'s as the client and server `objectId`'s may be generated using
      different algorithms. This can also lead to overwriting of `ParseObject`'s by accident as the
      client-side checks are disabled. Developers are responsible for handling such cases.
     */
@@ -179,8 +179,8 @@ public extension Sequence where Element: ParseObject {
      `isIgnoreCustomObjectIdConfig = false`. Setting
      `ParseConfiguration.allowCustomObjectId = true` and
      `isIgnoreCustomObjectIdConfig = true` means the client will generate `objectId`'s
-     and the server will generate an `objectId` only when the client does not provide one. This can lead
-     to collisions of `objectId`'s as the client and server `objectId`'s may be generated using
+     and the server will generate an `objectId` only when the client does not provide one. This can
+     increase the probability of colliiding `objectId`'s as the client and server `objectId`'s may be generated using
      different algorithms. This can also lead to overwriting of `ParseObject`'s by accident as the
      client-side checks are disabled. Developers are responsible for handling such cases.
     */
@@ -625,8 +625,8 @@ extension ParseObject {
      `isIgnoreCustomObjectIdConfig = false`. Setting
      `ParseConfiguration.allowCustomObjectId = true` and
      `isIgnoreCustomObjectIdConfig = true` means the client will generate `objectId`'s
-     and the server will generate an `objectId` only when the client does not provide one. This can lead
-     to collisions of `objectId`'s as the client and server `objectId`'s may be generated using
+     and the server will generate an `objectId` only when the client does not provide one. This can
+     increase the probability of colliiding `objectId`'s as the client and server `objectId`'s may be generated using
      different algorithms. This can also lead to overwriting of `ParseObject`'s by accident as the
      client-side checks are disabled. Developers are responsible for handling such cases.
     */
@@ -673,8 +673,8 @@ extension ParseObject {
      `isIgnoreCustomObjectIdConfig = false`. Setting
      `ParseConfiguration.allowCustomObjectId = true` and
      `isIgnoreCustomObjectIdConfig = true` means the client will generate `objectId`'s
-     and the server will generate an `objectId` only when the client does not provide one. This can lead
-     to collisions of `objectId`'s as the client and server `objectId`'s may be generated using
+     and the server will generate an `objectId` only when the client does not provide one. This can
+     increase the probability of colliiding `objectId`'s as the client and server `objectId`'s may be generated using
      different algorithms. This can also lead to overwriting of `ParseObject`'s by accident as the
      client-side checks are disabled. Developers are responsible for handling such cases.
     */

Sources/ParseSwift/Objects/ParseUser+combine.swift

@@ -171,8 +171,8 @@ public extension ParseUser {
      `isIgnoreCustomObjectIdConfig = false`. Setting
      `ParseConfiguration.allowCustomObjectId = true` and
      `isIgnoreCustomObjectIdConfig = true` means the client will generate `objectId`'s
-     and the server will generate an `objectId` only when the client does not provide one. This can lead
-     to collisions of `objectId`'s as the client and server `objectId`'s may be generated using
+     and the server will generate an `objectId` only when the client does not provide one. This can
+     increase the probability of colliiding `objectId`'s as the client and server `objectId`'s may be generated using
      different algorithms. This can also lead to overwriting of `ParseObject`'s by accident as the
      client-side checks are disabled. Developers are responsible for handling such cases.
     */
@@ -243,8 +243,8 @@ public extension Sequence where Element: ParseUser {
      `isIgnoreCustomObjectIdConfig = false`. Setting
      `ParseConfiguration.allowCustomObjectId = true` and
      `isIgnoreCustomObjectIdConfig = true` means the client will generate `objectId`'s
-     and the server will generate an `objectId` only when the client does not provide one. This can lead
-     to collisions of `objectId`'s as the client and server `objectId`'s may be generated using
+     and the server will generate an `objectId` only when the client does not provide one. This can
+     increase the probability of colliiding `objectId`'s as the client and server `objectId`'s may be generated using
      different algorithms. This can also lead to overwriting of `ParseObject`'s by accident as the
      client-side checks are disabled. Developers are responsible for handling such cases.
     */

Sources/ParseSwift/Objects/ParseUser.swift

@@ -826,8 +826,8 @@ extension ParseUser {
      `isIgnoreCustomObjectIdConfig = false`. Setting
      `ParseConfiguration.allowCustomObjectId = true` and
      `isIgnoreCustomObjectIdConfig = true` means the client will generate `objectId`'s
-     and the server will generate an `objectId` only when the client does not provide one. This can lead
-     to collisions of `objectId`'s as the client and server `objectId`'s may be generated using
+     and the server will generate an `objectId` only when the client does not provide one. This can
+     increase the probability of colliiding `objectId`'s as the client and server `objectId`'s may be generated using
      different algorithms. This can also lead to overwriting of `ParseObject`'s by accident as the
      client-side checks are disabled. Developers are responsible for handling such cases.
     */
@@ -877,8 +877,8 @@ extension ParseUser {
      `isIgnoreCustomObjectIdConfig = false`. Setting
      `ParseConfiguration.allowCustomObjectId = true` and
      `isIgnoreCustomObjectIdConfig = true` means the client will generate `objectId`'s
-     and the server will generate an `objectId` only when the client does not provide one. This can lead
-     to collisions of `objectId`'s as the client and server `objectId`'s may be generated using
+     and the server will generate an `objectId` only when the client does not provide one. This can
+     increase the probability of colliiding `objectId`'s as the client and server `objectId`'s may be generated using
      different algorithms. This can also lead to overwriting of `ParseObject`'s by accident as the
      client-side checks are disabled. Developers are responsible for handling such cases.
     */
@@ -1058,8 +1058,8 @@ public extension Sequence where Element: ParseUser {
      `isIgnoreCustomObjectIdConfig = false`. Setting
      `ParseConfiguration.allowCustomObjectId = true` and
      `isIgnoreCustomObjectIdConfig = true` means the client will generate `objectId`'s
-     and the server will generate an `objectId` only when the client does not provide one. This can lead
-     to collisions of `objectId`'s as the client and server `objectId`'s may be generated using
+     and the server will generate an `objectId` only when the client does not provide one. This can
+     increase the probability of colliiding `objectId`'s as the client and server `objectId`'s may be generated using
      different algorithms. This can also lead to overwriting of `ParseObject`'s by accident as the
      client-side checks are disabled. Developers are responsible for handling such cases.
     */
@@ -1158,8 +1158,8 @@ public extension Sequence where Element: ParseUser {
      `isIgnoreCustomObjectIdConfig = false`. Setting
      `ParseConfiguration.allowCustomObjectId = true` and
      `isIgnoreCustomObjectIdConfig = true` means the client will generate `objectId`'s
-     and the server will generate an `objectId` only when the client does not provide one. This can lead
-     to collisions of `objectId`'s as the client and server `objectId`'s may be generated using
+     and the server will generate an `objectId` only when the client does not provide one. This can
+     increase the probability of colliiding `objectId`'s as the client and server `objectId`'s may be generated using
      different algorithms. This can also lead to overwriting of `ParseObject`'s by accident as the
      client-side checks are disabled. Developers are responsible for handling such cases.
     */

Sources/ParseSwift/Storage/KeychainStore.swift

@@ -19,7 +19,7 @@ func getKeychainQueryTemplate(forService service: String) -> [String: String] {
         query[kSecAttrService as String] = service
     }
     query[kSecClass as String] = kSecClassGenericPassword as String
-    query[kSecAttrAccessible as String] =  kSecAttrAccessibleAfterFirstUnlockThisDeviceOnly as String
+    query[kSecAttrAccessible as String] = kSecAttrAccessibleAfterFirstUnlockThisDeviceOnly as String
     return query
 }