[libxslt] Fix typos in win32/Readme.txt
- From: Nick Wellnhofer <nwellnhof src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [libxslt] Fix typos in win32/Readme.txt
- Date: Wed, 7 Sep 2022 17:45:47 +0000 (UTC)
commit e1dbb994932ab282acdc122b853062c8dfb8c32c
Author: Christoph M. Becker <cmbecker69 gmx de>
Date: Wed Sep 7 16:02:08 2022 +0200
Fix typos in win32/Readme.txt
* allready → already
* ýou → you
win32/Readme.txt | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
---
diff --git a/win32/Readme.txt b/win32/Readme.txt
index e979294f..2a6a97c1 100644
--- a/win32/Readme.txt
+++ b/win32/Readme.txt
@@ -84,8 +84,8 @@ what in Gods name do I mean with '*.h files and their *.h.in sources',
then you really should do an automatic configuration. Which files must
be generated and what needs to be done with their sources in order to
generate them is something people who have built this software before
-allready know. You will not find any explanations for that
-here. Please configure the source manually only if you allready know
+already know. You will not find any explanations for that
+here. Please configure the source manually only if you already know
what you must do. Otherwise, you have the choice of either getting a
precompiled binary distribution, or performing the automatic
configuration.
@@ -98,7 +98,7 @@ After the configuration stage has been completed, you want to build
the software. You will have to use the make tool which comes with
your compiler. If you, for example, configured the source to build
with Microsoft's MSVC compiler, you would use the NMAKE utility. If
-�ou configured it to build with GNU C compiler, mingw edition, you
+you configured it to build with GNU C compiler, mingw edition, you
would use the GNU make. Assuming you use MSVC, type
nmake
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]