regcomp.c: White-space only

[perl5.git] / README.win32

diff --git a/README.win32 b/README.win32
index e2b9135..73d74bd 100644 (file)
--- a/README.win32
+++ b/README.win32
@@ -127,7 +127,7 @@ build usually works in this circumstance, but some tests will fail.
 
 The nmake that comes with Visual C++ will suffice for building. Visual C++
 requires that certain things be set up in the console before Visual C++ will
-sucessfully run. To make a console box be able to run the C compiler, you will
+successfully run. To make a console box be able to run the C compiler, you will
 need to beforehand, run C<vcvarsall.bat x86> to compile for x86-32 and for
 x86-64 C<vcvarsall.bat amd64>. On a typical install of a Microsoft C++
 compiler product, these batch files will already be in your C<PATH>
@@ -135,7 +135,7 @@ environment variable so you may just type them without an absolute path into
 your console. If you need to find the absolute path to the batch file, it is
 usually found somewhere like
 C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC.
-With some newer Micrsoft C products (released after ~2004), the installer will
+With some newer Microsoft C products (released after ~2004), the installer will
 put a shortcut in the start menu to launch a new console window with the
 console already set up for your target architecture (x86-32 or x86-64 or IA64).
 With the newer compilers, you may also use the older batch files if you choose
@@ -399,7 +399,7 @@ Be sure to read the instructions near the top of the makefiles carefully.
 Type "dmake" ("gmake" for GNU make, or "nmake" if you are using that make).
 
 This should build everything.  Specifically, it will create perl.exe,
-perl531.dll at the perl toplevel, and various other extension dll's
+perl533.dll at the perl toplevel, and various other extension dll's
 under the lib\auto directory.  If the build fails for any reason, make
 sure you have done the previous steps correctly.
 
@@ -882,7 +882,7 @@ L<https://github.com/Perl/perl5/issues>.
 Norton AntiVirus interferes with the build process, particularly if
 set to "AutoProtect, All Files, when Opened". Unlike large applications
 the perl build process opens and modifies a lot of files. Having the
-the AntiVirus scan each and every one slows build the process significantly.
+AntiVirus scan each and every one slows build the process significantly.
 Worse, with PERLIO=stdio the build process fails with peculiar messages
 as the virus checker interacts badly with miniperl.exe writing configure
 files (it seems to either catch file part written and treat it as suspicious,
@@ -922,8 +922,8 @@ Thus, signals may work only for simple things like setting a flag
 variable in the handler.  Using signals under this port should
 currently be considered unsupported.
 
-Please send detailed descriptions of any problems and solutions that
-you may find to E<lt>L<https://github.com/Perl/perl5/issues>E<gt>,
+Please report detailed descriptions of any problems and solutions that
+you may find at E<lt>L<https://github.com/Perl/perl5/issues>E<gt>,
 along with the output produced by C<perl -V>.
 
 =head1 ACKNOWLEDGEMENTS