File tidies for 8.20-RC2 release.

git-svn-id: svn://vcs.exim.org/pcre/code/trunk@708 2f5784b3-3f2a-0410-8824-cb99058d5e15

1 files changed, 4 insertions, 4 deletions

diff --git a/doc/pcrejit.3 b/doc/pcrejit.3
index 4620b6e..bf53f1b 100644
--- a/doc/pcrejit.3
+++ b/doc/pcrejit.3
@@ -79,7 +79,7 @@ JIT compilation was successful. A result of 0 means that JIT support is not
 available, or the pattern was not studied with PCRE_STUDY_JIT_COMPILE, or the
 JIT compiler was not able to handle the pattern.
 .P
-Once a pattern has been studied, with or without JIT, it can be used as many 
+Once a pattern has been studied, with or without JIT, it can be used as many
 times as you like for matching different subject strings.
 .
 .
@@ -134,16 +134,16 @@ execution.
 .rs
 .sp
 The code that is generated by the JIT compiler is architecture-specific, and is
-also position dependent. For those reasons it cannot be saved (in a file or 
+also position dependent. For those reasons it cannot be saved (in a file or
 database) and restored later like the bytecode and other data of a compiled
-pattern. Saving and restoring compiled patterns is not something many people 
+pattern. Saving and restoring compiled patterns is not something many people
 do. More detail about this facility is given in the
 .\" HREF
 \fBpcreprecompile\fP
 .\"
 documentation. It should be possible to run \fBpcre_study()\fP on a saved and
 restored pattern, and thereby recreate the JIT data, but because JIT
-compilation uses significant resources, it is probably not worth doing this; 
+compilation uses significant resources, it is probably not worth doing this;
 you might as well recompile the original pattern.
 .
 .