Just reflow, re-check #2695

Author: JJ

doc/Language/nativetypes.pod6

@@ -89,7 +89,8 @@ say @letter-pairs.perl;
 # OUTPUT: «array[str].new(:shape(10,), ["aA", "bB", "cC", "dD", "eE", "fF", "gG", "hH", "iI", "jJ"])␤»
 =end code
 
-X<|int8>X<|int16>X<|int32>X<|int64>X<|uint8>X<|uint16>X<|uint32>X<|uint64>X<|num32>X<|num64>X<|byte>
+X<|int8>X<|int16>X<|int32>X<|int64>X<|uint8>X<|uint16>X<|uint32>X<|uint64>
+X<|num32>X<|num64>X<|byte>
 =head1 Types with native representation and size
 
 What has been mentioned about types with native representation also applies

doc/Language/performance.pod6

@@ -58,16 +58,16 @@ profiled in the "Name" search box.
 The "Call Graph" section gives a flame graph representation of much of the same
 information as the "Routines" section.
 
-The "Allocations" section gives you information about the amount of different types
-that were allocated, as well as which routines did the allocating.
+The "Allocations" section gives you information about the amount of different
+types that were allocated, as well as which routines did the allocating.
 
 The "GC" section gives you detailed information about all the garbage
 collections that occurred.
 
-The "OSR / Deopt" section gives you information about On Stack Replacements (OSRs),
-which is when routines are "upgraded" from interpreted to speshed or jitted. Deopts
-are the opposite, when speshed or jitted code has to be "downgraded" to being
-interpreted.
+The "OSR / Deopt" section gives you information about On Stack Replacements
+(OSRs), which is when routines are "upgraded" from interpreted to speshed or
+jitted. Deopts are the opposite, when speshed or jitted code has to be
+"downgraded" to being interpreted.
 
 If the profile data is too big, it could take a long time for a browser to open
 the file. In that case, output to a file with a C<.json> extension using the
@@ -153,8 +153,8 @@ L<camelia|/language/glossary#camelia>.
 
 =head2 Routine by routine
 
-With multidispatch, you can drop in new variants of routines "alongside" existing
-ones:
+With multidispatch, you can drop in new variants of routines "alongside"
+existing ones:
 
     # existing code generically matches a two arg foo call:
     multi sub foo(Any $a, Any $b) { ... }

doc/Language/traits.pod6

@@ -63,7 +63,8 @@ cannot create an instance of this type (don't-instantiate)>.
 
 Since the C<is> trait refers, in general, to the nature of the class or object
 they are applied to, they are used extensively in
-L<native calls|/language/nativecall> to L<specify the representation|/language/nativecall#Specifying_the_native_representation>
+L<native calls|/language/nativecall> to
+L<specify the representation|/language/nativecall#Specifying_the_native_representation>
 of the data structures that are going to be handled by the native functions via
 the C<is repr> suffix; at the same time, C<is native> is used for the routines
 that are actually implemented via native functions. These are the