ppc0025: copyedit and relocate the new paragraph

Author: ap

ppcs/ppc0025-perl-version.md

@@ -56,8 +56,6 @@ That is the future. Perl will not have a successor. It will not break with its p
 
 Relations between Perl and Raku may (and should, and hopefully will) adjust to each other’s new self-understanding. In time, the family should rebalance into a new equilibrium, as family systems do. Perl and Raku can and should stay in touch and take inspiration from each other, even if each needs its features designed for cohesion with its own overall design.
 
-Among approaches for increasing the major version number of Perl, this one is least costly: the `PERL_REVISION` XS symbol can be left unchanged, which avoids having to update a lot of XS code that would otherwise break. Any other approach will incur this additional cost. So if going to version 42 is not feasible due to the amount of breakage then going to any other version will be even less feasible. Perl will in that case have to remain Perl 5 forever.
-
 This type of re-versioning has some precedents:
 
 * Java 1.4 was followed by Java 5. The technical details of that transition differ from what is proposed here, but even there we have a parallel between how Java 5 was mostly still 1.5 internally and how this proposal deals with XS code. Lessons can be had from the unlikeliest of sources.
@@ -66,6 +64,8 @@ This type of re-versioning has some precedents:
 
 Version 42 specifically is a particularly compelling point in time at which to do this, and not just for the Douglas Adams reference which will be evident even to Perl outsiders: there are further points of significance within Perl culture too, particularly when it comes to versions. 42 happens to be 6 × 7, and in ASCII, 42 (and thus the v-string `v42`) happens to be `*`. From a technical perspective, it is also opportune to undergo this transition well before version 48, at which point the fact that `v48 eq '0'` (and `v50 eq '2'` etc.) might cause unanticipated heartburn – so it is useful to have time to have any potential fallout sorted out well ahead of that.
 
+Note that among approaches for increasing the major version number of Perl, this one is least costly: because it can be implemented while leaving the `PERL_REVISION` XS symbol unchanged, it does not require updating a lot of XS code which would otherwise break. Any other approach will break all that XS code in addition to any other breakage it may cause, which almost certainly will include all of the breakage of this proposal. So if going to version 42 is not feasible due to the amount of breakage, then going to any other version will be much less feasible still, and Perl will have to remain Perl 5 forever.
+
 ## Specification
 
 In the next release of Perl, `perl -v` will not say “Perl 5 version 42 subversion 0” but simply “Perl version 42.0”.