Remove use of GetVolumeInformation since it causes long delays on network drives.

[wxWidgets.git] / docs / latex / wx / tfontenc.tex

diff --git a/docs/latex/wx/tfontenc.tex b/docs/latex/wx/tfontenc.tex
index b83964d8c2634dc9381d3713996228ce2423ab6b..da8af4e866d3c08450003e6aaef178ee78d9f4d3 100644 (file)
--- a/docs/latex/wx/tfontenc.tex
+++ b/docs/latex/wx/tfontenc.tex
@@ -11,7 +11,7 @@
 
 \section{Font encoding overview}\label{wxfontencodingoverview}
 
-wxWindows has support for multiple font encodings starting from release 2.2.
+wxWidgets has support for multiple font encodings starting from release 2.2.
 By encoding we mean here the mapping between the character codes and the
 letters. Probably the most well-known encoding is (7 bit) ASCII one which is
 used almost universally now to represent the letters of the English alphabet
@@ -20,7 +20,7 @@ letters of foreign alphabets and here other encodings come into play. Please
 note that we will only discuss 8-bit fonts here and not 
 \helpref{Unicode}{unicode}.
 
-Font encoding support is assured by several classes: 
+Font encoding support is ensured by several classes: 
 \helpref{wxFont}{wxfont} itself, but also 
 \helpref{wxFontEnumerator}{wxfontenumerator} and 
 \helpref{wxFontMapper}{wxfontmapper}. wxFont encoding support is reflected by
@@ -76,7 +76,7 @@ To solve this problem, a \helpref{wxFontMapper}{wxfontmapper} class is provided.
 This class stores the mapping between the encodings and the font face
 names which support them in \helpref{wxConfig}{wxconfigoverview} object. Of
 course, it would be fairly useless if it tried to determine these mappings by
-itself, so, instead, it (optionally) ask the user and remember his answers
+itself, so, instead, it (optionally) asks the user and remembers his answers
 so that the next time the program will automatically choose the correct font.
 
 All these topics are illustrated by the \helpref{font sample}{samplefont};