Formatting improvements

BREAKING-CHANGES.txt

@@ -10,8 +10,8 @@ Viewport now enables "scroll on drag" mode by default on Android and iOS.
 
 Possible Issues
 ---------------
-Any code relying on "scroll on drag" mode being turned off by default, should disable
-it manually.
+Any code relying on "scroll on drag" mode being turned off by default, should
+disable it manually.
 
 Workaround
 ----------
@@ -20,33 +20,33 @@ None.
 Rationale
 ---------
 It is expected on mobile devices to be able to scroll a list by just a drag,
-rather than using a dedicated scrollbar. The scrollbar is still available though if
-needed.
+rather than using a dedicated scrollbar. The scrollbar is still available
+though if needed.
 
 
 Change
 ------
-The previous setting of Android exporter "Custom manifest xml elements" creating
-child nodes of <application> element has been replaced by "Custom manifest XML content"
-setting that allows to specify the content of the entire manifest instead.
-Any previously values of the old setting will be used in the new setting by default, and
-they will need changing as mentioned in Workaround. The custom content will be merged
-with the content auto-generated by Projucer. Any custom elements or custom attributes
-will override the ones set by Projucer. Projucer will also automatically add any
-missing and required elements and attributes.
-
+The previous setting of Android exporter "Custom manifest xml elements"
+creating child nodes of <application> element has been replaced by "Custom
+manifest XML content" setting that allows to specify the content of the entire
+manifest instead.  Any previously values of the old setting will be used in the
+new setting by default, and they will need changing as mentioned in Workaround.
+The custom content will be merged with the content auto-generated by Projucer.
+Any custom elements or custom attributes will override the ones set by
+Projucer. Projucer will also automatically add any missing and required
+elements and attributes.
 
 Possible Issues
 ---------------
-If a Projucer project used "Custom manifest xml elements" field, the value will no
-longer be compatible with the project generated in the latest Projucer version. The solution
-is very simple and quick though, as mentioned in the Workaround section.
-
+If a Projucer project used "Custom manifest xml elements" field, the value will
+no longer be compatible with the project generated in the latest Projucer
+version. The solution is very simple and quick though, as mentioned in the
+Workaround section.
 
 Workaround
 ----------
-For any elements previously used, simply embed them explicitly in <manifest><application>
-elements,for example instead of:
+For any elements previously used, simply embed them explicitly in
+<manifest><application> elements,for example instead of:
 
 <meta-data android:name="paramId1" android:value="paramValue1"/>
 <meta-data android:name="paramId2" android:value="paramValue2"/>
@@ -60,15 +60,15 @@ simply write:
 </application>
 </manifest>
 
-
 Rationale
 ---------
-To maintain the high level of flexibility of generated Android projects and to avoid
-creating fields in Projucer for every possible future parameter, it is simpler to allow to
-set up the required parameters manually. This way it is not only possible to add any custom
-elements but it is also possible to override the default attributes assigned by Projucer for
-the required elements. For instance, if the default value of <supports-screens> element is
-not satisfactory because you want a support for x-large screens only, simply set
+To maintain the high level of flexibility of generated Android projects and to
+avoid creating fields in Projucer for every possible future parameter, it is
+simpler to allow to set up the required parameters manually. This way it is not
+only possible to add any custom elements but it is also possible to override
+the default attributes assigned by Projucer for the required elements. For
+instance, if the default value of <supports-screens> element is not
+satisfactory because you want a support for x-large screens only, simply set
 "Custom manifest XML content" to:
 
 <manifest>

ChangeList.txt

@@ -93,7 +93,7 @@ Version 5.0.0
   - Added support for IPv6
   - Various minor improvements and bug fixes
   - Various documentation improvements
- 
+
 Version 4.3.1
   - Added support for iOS download tasks
   - Added support for AAX plug-in meters

examples/InAppPurchase/Signing/README.txt

@@ -1,5 +1,5 @@
-This signing key is used to sign the android version of the in-app purchase sample app so that authenticated requests to the play store API can be tested.
-
-This key has only been used to sign the in-app purchase sample app and therefore cannot be used for any other apps. It’s impossible to use to sign any existing apps on the app store.
-
-! Do not use this key for your own production apps !
+This signing key is used to sign the android version of the in-app purchase sample app so that authenticated requests to the play store API can be tested.
+
+This key has only been used to sign the in-app purchase sample app and therefore cannot be used for any other apps. It’s impossible to use to sign any existing apps on the app store.
+
+! Do not use this key for your own production apps !