summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/latex/beamer/beamerug-tutorial.tex
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/latex/beamer/beamerug-tutorial.tex')
-rw-r--r--Master/texmf-dist/doc/latex/beamer/beamerug-tutorial.tex6
1 files changed, 3 insertions, 3 deletions
diff --git a/Master/texmf-dist/doc/latex/beamer/beamerug-tutorial.tex b/Master/texmf-dist/doc/latex/beamer/beamerug-tutorial.tex
index fecbffccc31..9dad541ac3e 100644
--- a/Master/texmf-dist/doc/latex/beamer/beamerug-tutorial.tex
+++ b/Master/texmf-dist/doc/latex/beamer/beamerug-tutorial.tex
@@ -167,9 +167,9 @@ The frame already looks quite nice, though, perhaps a bit colorful. However, Euc
\end{itemize}
\end{verbatim}
-By showing them incrementally, he hopes to focus the audience's attention on the item he is currently talking about. On second thought, he deletes the |\pause| stuff once more since in simple cases like the above the pausing is rather silly. Indeed, Euclids has noticed that good presentations make use of this uncovering mechanism only in special circumstances.
+By showing them incrementally, he hopes to focus the audience's attention on the item he is currently talking about. On second thought, he deletes the |\pause| stuff once more since in simple cases like the above the pausing is rather silly. Indeed, Euclid has noticed that good presentations make use of this uncovering mechanism only in special circumstances.
-Euclid finds that he can also add a |\pause| between the definition and the example. So, |\pause|s seem to transcede environments, which Euclid finds quite useful. After some experimentation he finds that |\pause| only does not work in |align| environments. He immediately writes an email about this to \beamer's author, but receives a polite answer stating that the implementation of |align| does wicked things and there is no fix for this. Also, Euclid is pointed to the last part of the user's guide, where a workaround is described.
+Euclid finds that he can also add a |\pause| between the definition and the example. So, |\pause|s seem to transcend environments, which Euclid finds quite useful. After some experimentation he finds that |\pause| only does not work in |align| environments. He immediately writes an email about this to \beamer's author, but receives a polite answer stating that the implementation of |align| does wicked things and there is no fix for this. Also, Euclid is pointed to the last part of the user's guide, where a workaround is described.
\subsection{Using Overlay Specifications}
@@ -354,7 +354,7 @@ On second thought, Euclid would prefer to uncover part of the algorithm stepwise
\visible<4->{Note the use of \alert{\texttt{std::}}.}
\end{frame}
\end{verbatim}
-The |\visible| command does nearly the same as |\uncover|. A difference occurs if the command |\setbeamercovered{transparent}| has been used to make covered text ``transparent'' instead, |\visible| still makes the text completely ``invisible'' on non-specified slides. Euclid has the feeling that the naming convention is a bit strange, but cannot quite pinpoint the problem.
+The |\visible| command does nearly the same as |\uncover|. However one difference occurs if the command |\setbeamercovered{transparent}| has been used to make covered text ``transparent'' instead, |\visible| still makes the text completely ``invisible'' on non-specified slides. Euclid has the feeling that the naming convention is a bit strange, but cannot quite pinpoint the problem.
\subsection{Changing the Way Things Look I: Theming}