Reworded android known issues

www/_posts/TBD-cordova-plugin-camera-8.0.0.md

@@ -105,8 +105,9 @@ Users using the `allowEdit` feature should move to a dedicated image manipulatio
 #### iOS 
 
 The `FileEntry.toURL` method on iOS does not produce a DOM-usable uri while
-the application is configured to use schemes. A [fix](https://github.com/apache/cordova-plugin-file/pull/642) for this will be available
-at an later date. In the meantime, the following can be used as a workaround:
+the application is configured to use schemes. A [fix](https://github.com/apache/cordova-plugin-file/pull/642)
+for this will be available at an later date. In the meantime, the following can
+be used as a workaround:
 
 ```javascript
 // TODO: Remove when https://github.com/apache/cordova-plugin-file/pull/642 is released
@@ -120,15 +121,18 @@ function toDomURL(fileEntry) {
 }
 ```
 
-If your app is still hosted on the `file://` protocol on iOS, then the workaround is not necessary.
+If your app is still hosted on the `file://` protocol on iOS, then the
+workaround is not necessary.
 
 #### Android
 
-Android will start returning `content://` URIs when selecting images from the user's gallery.
-Instead of `file://` in order to make use of the underlying MediaStore APIs.
-In order for these paths to be resolvable to a DOM-usable URL, `AndroidInsecureFileModeEnabled` must be off (the default value).
+Android will start returning `content://` instead of `file://` URIs when
+selecting images from the user's gallery in order to make use of the underlying
+MediaStore APIs. In order for these paths to be resolvable to a DOM-usable URL,
+`AndroidInsecureFileModeEnabled` must be off (the default value).
 
-Please report any issues you find by following the [How to File a Bug](https://github.com/apache/cordova#filing-a-bug) guide!
+Please report any issues you find by following the
+[How to File a Bug](https://github.com/apache/cordova#filing-a-bug) guide!
 
 <!--more-->
 # Changes include: