Name change replacements

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

diff --git a/docs/latex/wx/tbitmap.tex b/docs/latex/wx/tbitmap.tex
index a9e751a9eeac2459b0221089d3ec888ab190b3d3..22788f246de47c74e7b66c2dbe003776fbed1691 100644 (file)
--- a/docs/latex/wx/tbitmap.tex
+++ b/docs/latex/wx/tbitmap.tex
@@ -18,7 +18,7 @@ version of the graphic which appears on the main window.
 
 See \helpref{wxMemoryDC}{wxmemorydc} for an example of drawing onto a bitmap.
 
 
 See \helpref{wxMemoryDC}{wxmemorydc} for an example of drawing onto a bitmap.
 

-All wxWindows platforms support XPMs for small bitmaps and icons.
+All wxWidgets platforms support XPMs for small bitmaps and icons.

 You may include the XPM inline as below, since it's C code, or you
 can load it at run-time.
 
 You may include the XPM inline as below, since it's C code, or you
 can load it at run-time.
 


@@ -76,7 +76,7 @@ The following lists the formats handled on different platforms. Note
 that missing or partially-implemented formats are automatically supplemented
 by the \helpref{wxImage}{wximage} to load the data, and then converting
 it to wxBitmap form. Note that using wxImage is the preferred way to
 that missing or partially-implemented formats are automatically supplemented
 by the \helpref{wxImage}{wximage} to load the data, and then converting
 it to wxBitmap form. Note that using wxImage is the preferred way to

-load images in wxWindows, with the exception of resources (XPM-files or
+load images in wxWidgets, with the exception of resources (XPM-files or

 native Windows resources). Writing an image format handler for wxImage
 is also far easier than writing one for wxBitmap, because wxImage has
 exactly one format on all platforms whereas wxBitmap can store pixel data
 native Windows resources). Writing an image format handler for wxImage
 is also far easier than writing one for wxBitmap, because wxImage has
 exactly one format on all platforms whereas wxBitmap can store pixel data