Remove wrong information related to changes in float tokenisation.

Author: johnkjellberg

_overviews/tutorials/scala-for-java-programmers.md

@@ -167,27 +167,11 @@ arithmetic expression like the following:
 consists exclusively of method calls, because it is equivalent to the
 following expression, as we saw in the previous section:
 
-    (1).+(((2).*(3))./(x))
+    1.+(2.*(3)./(x))
 
 This also means that `+`, `*`, etc. are valid identifiers
 in Scala.
 
-The parentheses around the numbers in the second version are necessary
-because Scala's lexer uses a longest match rule for tokens.
-Therefore, it would break the following expression:
-
-    1.+(2)
-
-into the tokens `1.`, `+`, and `2`.  The reason that
-this tokenization is chosen is because `1.` is a longer valid
-match than `1`.  The token `1.` is interpreted as the
-literal `1.0`, making it a `Double` rather than an
-`Int`.  Writing the expression as:
-
-    (1).+(2)
-
-prevents `1` from being interpreted as a `Double`.
-
 ### Functions are objects
 
 Functions are also