X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/f52e0cf4893f90451eaf5987e4786bde066f629c..b70b68a9ba62320a6a667f510b316219c7029d90:/docs/latex/wx/sizer.tex?ds=inline

diff --git a/docs/latex/wx/sizer.tex b/docs/latex/wx/sizer.tex
index 984889707b..fcb072378c 100644
--- a/docs/latex/wx/sizer.tex
+++ b/docs/latex/wx/sizer.tex
@@ -4,10 +4,10 @@ wxSizer is the abstract base class used for laying out subwindows in a window. Y
 cannot use wxSizer directly; instead, you will have to use one of the sizer
 classes derived from it. Currently there are \helpref{wxBoxSizer}{wxboxsizer}, 
 \helpref{wxStaticBoxSizer}{wxstaticboxsizer},
-\helpref{wxNotebookSizer}{wxnotebooksizer}, \helpref{wxGridSizer}{wxgridsizer} 
-and \helpref{wxFlexGridSizer}{wxflexgridsizer}.
+\helpref{wxGridSizer}{wxgridsizer} 
+\helpref{wxFlexGridSizer}{wxflexgridsizer} and \helpref{wxGridBagSizer}{wxgridbagsizer}.
 
-The layout algorithm used by sizers in wxWindows is closely related to layout
+The layout algorithm used by sizers in wxWidgets is closely related to layout
 in other GUI toolkits, such as Java's AWT, the GTK toolkit or the Qt toolkit. It is
 based upon the idea of the individual subwindows reporting their minimal required
 size and their ability to get stretched if the size of the parent window has changed.
@@ -19,7 +19,7 @@ a hierarchy of sizers can be constructed. Note that wxSizer does not derive from
 and thus do not interfere with tab ordering and requires very little resources compared
 to a real window on screen.
 
-What makes sizers so well fitted for use in wxWindows is the fact that every control
+What makes sizers so well fitted for use in wxWidgets is the fact that every control
 reports its own minimal size and the algorithm can handle differences in font sizes
 or different window (dialog item) sizes on different platforms without problems. If e.g.
 the standard font as well as the overall design of Motif widgets requires more space than
@@ -107,17 +107,17 @@ dependent on the specific kind of sizer used.
 \windowstyle{wxALL}}{These flags are used to specify which side(s) of
   the sizer item the {\it border} width will apply to. }
 
-\twocolitem{\windowstyle{wxEXAPAND}}{The item will be expanded to fill
-the space allotted to the item.}
+\twocolitem{\windowstyle{wxEXPAND}}{The item will be expanded to fill
+the space assigned to the item.}
 \twocolitem{\windowstyle{wxSHAPED}}{The item will be expanded as much
 as possible while also maintaining its aspect ratio}
-\twocolitem{\windowstyle{wxFIXED\_MINSIZE}}{Normally wxSizers will use
-  \helpref{GetAdjustedBestSize}{wxwindowgetadjustedbestsize} to
-  determin what the minimal size of window items should be, and will
-  use that size to calculate the layout.  This allows layouts to
-  adjust when an item changes and it's {\it best size} becomes
-  different.  If you would rather have a window item stay the size it
-  started with then use wxFIXED\_MINSIZE.}
+\twocolitem{\windowstyle{wxFIXED\_MINSIZE}}{Normally wxSizers will use 
+\helpref{GetAdjustedBestSize}{wxwindowgetadjustedbestsize} to
+determine what the minimal size of window items should be, and will
+use that size to calculate the layout. This allows layouts to
+adjust when an item changes and its {\it best size} becomes
+different. If you would rather have a window item stay the size it
+started with then use wxFIXED\_MINSIZE.}
 \twocolitem{\windowstyle{wxALIGN\_CENTER}\\
 \windowstyle{wxALIGN\_LEFT}\\
 \windowstyle{wxALIGN\_RIGHT}\\
@@ -125,8 +125,8 @@ as possible while also maintaining its aspect ratio}
 \windowstyle{wxALIGN\_BOTTOM}\\
 \windowstyle{wxALIGN\_CENTER\_VERTICAL}\\
 \windowstyle{wxALIGN\_CENTER\_HORIZONTAL}}{The wxALIGN flags allow you to
-  specify the alignment of the item within the space allotted to it by
-  the sizer, ajusted for the border if any.}
+specify the alignment of the item within the space allotted to it by
+the sizer, adjusted for the border if any.}
 \end{twocollist}
 }
 
