I like if things compile with --enable-unicode + --enable-mediactrl. Code shamelessly...

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

diff --git a/docs/latex/wx/ttips.tex b/docs/latex/wx/ttips.tex
index 5dac6dd9113f39e01f89f2a6e8f86c2b61c5c4b0..5ccde7a4f94ed9d123a14577711dab5bde9d2db7 100644 (file)
--- a/docs/latex/wx/ttips.tex
+++ b/docs/latex/wx/ttips.tex
@@ -5,7 +5,7 @@ presenting the user tips at program startup. While this is probably useless to
 the advanced users of the program, the experience shows that the tips may be
 quite helpful for the novices and so more and more programs now do this.
 
-For a wxWindows programmer, implementing this feature is extremely easy. To
+For a wxWidgets programmer, implementing this feature is extremely easy. To
 show a tip, it is enough to just call \helpref{wxShowTip}{wxshowtip} function
 like this:
 
@@ -48,14 +48,16 @@ skipped.
 You can easily add runtime-translation capacity by placing each line of the 
 tips.txt file inside the usual translation macro. For example, your tips.txt 
 file would look like this:
+
 \begin{verbatim}
 _("This is my first tip")
 _("This is my second tip")
 \end{verbatim}
+
 Now add your tips.txt file into the list of files that gettext searches 
 for translatable strings. The tips will thus get included into your 
 generated .po file catalog and be translated at runtime along with the rest of 
-your aplication's translatable strings. 
+your application's translatable strings. 
 Note1: Each line in the tips.txt file needs to strictly begin with exactly the 
 3 characters of underscore-parenthesis-doublequote, and end with 
 doublequote-parenthesis, as shown above. 
@@ -64,3 +66,4 @@ a backslash-doublequote.
 
 See the dialogs program in your samples folder for a working example inside a 
 program.
+