Formatting fix.

Author: photonstorm

README.md

@@ -360,8 +360,7 @@ Please note that Phaser uses a custom build of Pixi and always has done. The fol
     relative to the targetCoordinateSpace DisplayObject.
 
 As a result this also fixes how empty Groups are treated when they have no other children except Groups. So now calculations are correct.
-* DisplayObjectContainer.contains(child) is a new method which determines whether the specified display object is a child of the DisplayObjectContainer instance or the instance itself. This method is
-used in the new getBounds function.
+* DisplayObjectContainer.contains(child) is a new method which determines whether the specified display object is a child of the DisplayObjectContainer instance or the instance itself. This method is used in the new getBounds function.
 * Corrected DisplayObjects default `_bounds` rect from (0, 0, 1, 1) to (0, 0, 0, 0).
 * Thanks to @fmflame for his hard work on the above (#2639 #2627)
 * The methods `setStageReference` and `removeStageReference` have been removed from all Pixi classes. Objects no longer have `stage` properties, or references to the Stage object. This is because no reference to the Stage is required for any calculations, and Phaser can only have 1 Stage, so adding and removing references to it were superfluous actions.

src/gameobjects/BitmapText.js

@@ -277,7 +277,8 @@ Phaser.BitmapText.prototype.scanLine = function (data, scale, text) {
             var kerning = (prevCharCode && charData.kerning[prevCharCode]) ? charData.kerning[prevCharCode] : 0;
 
             //  Record the last space in the string and the current width
-            if (/(\s)/.test(text.charAt(i))) {
+            if (/(\s)/.test(text.charAt(i)))
+            {
                 lastSpace = i;
                 wrappedWidth = w;
             }