More line wrap updates in the readme.

Signed-off-by: Kevin Deus <[email protected]>

README.md

@@ -43,23 +43,24 @@ provide the following building blocks
 - A light-weight _Secure Area_ abstraction for hardware-backed keystore
   - Applications can create hardware-backed Elliptic Curve Cryptography
     keys which can be used for creating Signatures or performing Key Agreement.
-    Each key will have an attestation which can be used to prove to Relying Parties
-    (such as a credential issuer) that the private part of the key only exists
-    in a Secure Area.
+    Each key will have an attestation which can be used to prove to Relying
+    Parties (such as a credential issuer) that the private part of the key
+    only exists in a Secure Area.
   - The `identity-android` library includes an implementation based on
     [Android Keystore](https://developer.android.com/training/articles/keystore)
-    with support for requiring user authentication (biometric or lock-screen knowledge
-    factor, e.g. system PIN) for unlocking the key and also can use
+    with support for requiring user authentication (biometric or lock-screen
+    knowledge factor, e.g. system PIN) for unlocking the key and also can use
     [StrongBox](https://source.android.com/docs/compatibility/13/android-13-cdd#9112_strongbox)
-    if available on the device. This is appropriate to use in Android applications
-    implementing ISO/IEC 18013-5:2021 for storing `DeviceKey`.
+    if available on the device. This is appropriate to use in Android
+    applications implementing ISO/IEC 18013-5:2021 for storing `DeviceKey`.
   - The `identity` library includes an implementation backed by BouncyCastle
     with support for passphrase-protected keys. This isn't suitable for use
     in Mobile Applications as its not backed by Secure Hardware.
   - A protocol for a Cloud Secure Area is provided along with production quality
-    client-side implementation in the `identity-android-csa` library and a reference
-    implementation of the server side in the `identity-csa` library with the caveat
-    that the provided server implementation isn't suitable for production use.
+    client-side implementation in the `identity-android-csa` library and a
+    reference implementation of the server side in the `identity-csa` library
+    with the caveat that the provided server implementation isn't suitable for
+    production use.
     - The point of this is to provide a secure and privacy-preserving protocol
       with end-to-end encryption directly from the app to a Secure Area
       in the server, with messages being exchanged via HTTPS. Consequently, this