Andrea and Andrew corrections and changed placements

[goodguy/cin-manual-latex.git] / parts / Stuff.tex

diff --git a/parts/Stuff.tex b/parts/Stuff.tex
index 250284e896b31354ab1bfcfc5e411c42f2863267..f89e3f0ec85958f3aabda5d111b8936d85af7ded 100644 (file)
--- a/parts/Stuff.tex
+++ b/parts/Stuff.tex
@@ -64,7 +64,7 @@ Simple explanation of what you will be seeing in the compositor when playing:
     \item[Play backward] the frame to the left of the cursor in the timeline gets displayed.
 \end{description}
 
-The reason behind this \textit{play} methodology is that you want to know what you just played so that you know what matches what you just saw/heard in case that is the desired stuff.   You don't want the compositor to show you what you have not yet played -- you need to see this frame to analyze/check to see if it is what you want.  This behavior applies to any playing operation, such as the \textit{keypad} or \textit{Frame forward / Frame reverse} buttons.  You can still easily see the actual insertion point in the zoombar at the bottom of the timeline -- sixth button over or 3rd button from the right side.   Also note the following:
+The reason behind this \textit{play} methodology is that you want to know what you just played so that you know what matches what you just saw/heard in case that is the desired stuff.   You don't want the compositor to show you what you have not yet played -- you need to see this frame to analyze/check to see if it is what you want.  This behavior applies to any playing operation, such as the \textit{keypad} or \textit{Frame forward / Frame reverse} buttons.  You can still easily see the actual insertion point in the zoombar at the bottom of the timeline -- seventh button over or 3rd button from the right side.   Also note the following:
 
 \begin{description}
     \item[Blinking insertion point on the timeline] seeking/positioning was the last operation.
@@ -173,8 +173,8 @@ click on the highlighted media and choosing \textit{Match project size}.
 However, this automatic method leads to the dilemma of where you have a 10-bit media file and it would
 get loaded as RGBA-8 when you would prefer it to be RGBA-Float.  So instead of using \textit{replace current
 project} when loading your media, you would have to make sure the project is first set to your desired
-Format.  This could be done with the File$\rightarrow$New project and then setting your Color
-Model to RGBA-Float and whatever other parameters you want.  Next when doing a File$\rightarrow$Load, use
+Format.  This could be done with the \texttt{File$\rightarrow$New project} and then setting your Color
+Model to RGBA-Float and whatever other parameters you want.  Next when doing a \texttt{File$\rightarrow$Load}, use
 \textit{Append in new tracks} or \textit{Create resources only}. This avoids using the "best model"
 technique and uses instead what you have designated so that if you set the Color Model to RGBA-Float that
 will be in effect.