Use 'base class subobject', not 'base subobject' (#1382)

Fixes #1379.

Author: jensmaurer

source/derived.tex

@@ -281,7 +281,7 @@
 {figvirt.pdf}
 \end{importgraphic}
 For an object \tcode{c} of class type \tcode{C}, a single subobject of
-type \tcode{V} is shared by every base subobject of \tcode{c} that has a
+type \tcode{V} is shared by every base class subobject of \tcode{c} that has a
 \tcode{virtual} base class of type \tcode{V}. Given the class \tcode{C}
 defined above, an object of class \tcode{C} will have one subobject of
 class \tcode{V}, as shown in Figure~\ref{fig:virt}.
@@ -418,7 +418,7 @@
 \end{codeblock}
 
 $S(x,F)$ is unambiguous because the \tcode{A} and \tcode{B} base
-subobjects of \tcode{D} are also base subobjects of \tcode{E}, so
+class subobjects of \tcode{D} are also base class subobjects of \tcode{E}, so
 $S(x,D)$ is discarded in the first merge step.
 \end{example}
 

source/iostreams.tex

@@ -1465,7 +1465,7 @@
 If the function fails\footnote{for example, because it cannot allocate space.}
 and
 \tcode{*this}
-is a base subobject of a
+is a base class subobject of a
 \tcode{basic_ios<>}
 object or subobject, the effect is equivalent to calling
 \tcode{basic_ios<>::setstate(badbit)}
@@ -1509,7 +1509,7 @@
 If the function fails\footnote{for example, because it cannot allocate space.}
 and
 \tcode{*this}
-is a base subobject of a
+is a base class subobject of a
 \tcode{basic_ios<>}
 object or subobject, the effect is equivalent to calling
 \tcode{basic_ios<>::setstate(badbit)}
@@ -6278,7 +6278,7 @@
 interface to iostreams, since for flexibility it has been abstracted
 away from direct dependence on
 \tcode{ostream}.
-The second parameter is a reference to the base subobject of type
+The second parameter is a reference to the base class subobject of type
 \tcode{ios_base}.
 It provides formatting specifications such as field width, and
 a locale from which to obtain other facets.

source/special.tex

@@ -1581,7 +1581,7 @@
 
 \pnum
 In the definition of a constructor for a class,
-initializers for direct and virtual base subobjects and
+initializers for direct and virtual base class subobjects and
 non-static data members can be specified by a
 \grammarterm{ctor-initializer},
 which has the form