IS_HATCH macro replaced with wxBrush::IsHatch() + source and docs little cleaning.

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

diff --git a/docs/latex/wx/txrc.tex b/docs/latex/wx/txrc.tex
index 11e6ef7eaa69cf28b4b8e7dc901febb59ea09578..f412029aaddbf93afc005c4db3055680e4fc53c9 100644 (file)
--- a/docs/latex/wx/txrc.tex
+++ b/docs/latex/wx/txrc.tex
@@ -95,7 +95,7 @@ For example:
 
 \wxheading{Note}
 
-XRS file is esentially a renamed ZIP archive which means that you can manipulate
+XRS file is essentially a renamed ZIP archive which means that you can manipulate
 it with standard ZIP tools. Note that if you are using XRS files, you have
 to initialize \helpref{wxFileSystem}{wxfilesystem} ZIP handler first! It is a simple
 thing to do:
@@ -120,7 +120,7 @@ contain a function called {\it InitXmlResource} (unless you override this with
 a command line switch). Use it to load the resource:
 
 \begin{verbatim}
-  extern void InitXMLResource(); // defined in generated file
+  extern void InitXmlResource(); // defined in generated file
   ...
   wxXmlResource::Get()->InitAllHandlers();
   InitXmlResource();
@@ -424,7 +424,7 @@ containing class definitions for the GUI windows defined in the XRC file.
 This code generation can make it easier to use XRC and automate program
 development.
 The classes can be used as basis for development, freeing the
-programmer from dealing with most of the XRC specifities (e.g. {\tt XRCCTRL}).
+programmer from dealing with most of the XRC specifics (e.g. {\tt XRCCTRL}).
 
 For each top level window defined in the XRC file a C++ class definition is
 generated, containing as class members the named widgets of the window.