[gtksourceview/win32-readme: 4/4] README.win32.md: Use UNIX line endings

[Chun-wei Fan <fanchunwei src gnome org>]

commit 32fb5fc6bfe70c49696fa2d8a837187c5834f939
Author: Chun-wei Fan <fanchunwei src gnome org>
Date:   Fri Jun 24 11:34:04 2022 +0800

    README.win32.md: Use UNIX line endings
    
    It is not that important to keep this file in Windows CR/LF line endings
    anymore, so use UNIX line endings to be consistent with the rest of the
    files here.

 README.win32.md | 38 +++++++++++++++++++-------------------
 1 file changed, 19 insertions(+), 19 deletions(-)
---
diff --git a/README.win32.md b/README.win32.md
index daba04c4..1c7817d8 100644
--- a/README.win32.md
+++ b/README.win32.md
@@ -4,7 +4,7 @@ Building GtkSourceView for Windows using Visual Studio
 Meson is now the supported method of building GtkSourceView with Visual Studio, where the process
 of doing so is described in the following section:
 
-Prior to building, you will need the following tools and programs:
+Prior to building, you will need the following tools and programs:
 
 - Python 3.6.x or later
 - Meson 0.59.0 (or later) at this time of writing
@@ -17,7 +17,7 @@ Prior to building, you will need the following tools and programs:
  such a tool.
 - CMake, either installed manually or as part of Visual Studio 2017 or later
  (optional, but recommended, to help locating dependencies)
-
+
 You will also need the following prerequesites installed:
 - GLib 2.70.0 (or later) at this time of writing
 - GTK 4.5.0 (or later) at this time of writing
@@ -25,19 +25,19 @@ You will also need the following prerequesites installed:
 - GObject-Introspection 1.70.0 (or later) at this time of writing [optional]
 
 For the depedent packages, you will need to ensure that their pkg-config (.pc) files
-could be found by the `pkg-config` utility, either directly or by passing in
-`--pkg-config-path=...` to point to the path(s) where the .pc files could be found in the
-Meson command line.  For libxml2, if .pc files are not available, ensure that its headers and
-import library can be found by ensuring your `%INCLUDE%` and `%LIB%` environment variables
-include these repective paths, and ensure that `cmake` is installed and in your `%PATH%`.
-For the introspection to complete successfully, you will also need to ensure that the DLLs
-can be found in the bindir entries of your .pc files or in your `%PATH%`.
-
-ARM64 Windows builds are also supported provided that a valid cross compilation config file
+could be found by the `pkg-config` utility, either directly or by passing in
+`--pkg-config-path=...` to point to the path(s) where the .pc files could be found in the
+Meson command line.  For libxml2, if .pc files are not available, ensure that its headers and
+import library can be found by ensuring your `%INCLUDE%` and `%LIB%` environment variables
+include these repective paths, and ensure that `cmake` is installed and in your `%PATH%`.
+For the introspection to complete successfully, you will also need to ensure that the DLLs
+can be found in the bindir entries of your .pc files or in your `%PATH%`.
+
+ARM64 Windows builds are also supported provided that a valid cross compilation config file
 is set up and passed into the Meson command line using `--cross-file=...`.
 
-#### Building GtkSourceView
-
+#### Building GtkSourceView
+
 Please do the following:
 
 - Open a Visual Studio command prompt.
@@ -45,7 +45,7 @@ Please do the following:
   as the GtkSourceView sources.
 - Run the command in the command prompt in your build directory:
    ```
-  meson <path_to_GtkSourceView_sources> --buildtype=... --prefix=... -Dvapi=false
+  meson <path_to_GtkSourceView_sources> --buildtype=... --prefix=... -Dvapi=false
   ```
  
  Where:
@@ -57,15 +57,15 @@ Please do the following:
 
  You may want to specify the following as well:
  -  `--backend=vs`: Generate Visual Studio projects for building on Visual Studio 2015
-                       2017, 2019 and 2022.  This will remove the need for Ninja.  Please
-                       note that the generated project files are only valid on the machine
-                       they are generated, and such builds may not be that well-supported
-                       by Meson.  Any issues that are found using this method but are not
+                       2017, 2019 and 2022.  This will remove the need for Ninja.  Please
+                       note that the generated project files are only valid on the machine
+                       they are generated, and such builds may not be that well-supported
+                       by Meson.  Any issues that are found using this method but are not
                        found using Ninja should be reported to the Meson project.
 
 If the previous command completed successfully, carry out the build by running `ninja` or
 by opening and building the projects with the generated Visual Studio projects, if using
-`--backend=vs`.  If desired, run the test using `ninja test` or building the `test`
+`--backend=vs`.  If desired, run the test using `ninja test` or building the `test`
 project in the Visual Studio projects.
 
 Install the build results using `ninja install` or building the `install` project in the