[musicians-guide] some simple clean-up

Christopher Antila crantila at fedoraproject.org
Sat May 19 22:22:27 UTC 2012


commit a28775d920e1ddda2063cd1a80751115b51ab93b
Author: Christopher Antila <crantila at fedoraproject.org>
Date:   Sat May 19 12:15:52 2012 -0400

    some simple clean-up

 en-US/Planet_CCRMA_at_Home.xml |   24 +++++++-----------------
 en-US/Qtractor.xml             |   18 +++++++++---------
 en-US/Revision_History.xml     |    4 +---
 3 files changed, 17 insertions(+), 29 deletions(-)
---
diff --git a/en-US/Planet_CCRMA_at_Home.xml b/en-US/Planet_CCRMA_at_Home.xml
index bc155fd..ed6ee7b 100644
--- a/en-US/Planet_CCRMA_at_Home.xml
+++ b/en-US/Planet_CCRMA_at_Home.xml
@@ -15,19 +15,12 @@
 		<para>
 			Users of GNU Solfege and LilyPond should not concern themselves with Planet CCRMA at Home, unless they also user other audio software.  Neither Solfege nor LilyPond would benefit from a computer optimzed for audio production.
 		</para>
-		<!-- Je pense que I don't need these sub-sections. -->
-		<!-- <section id="sect-Musicians_Guide-CCRMA">
-			<title>CCRMA</title> -->
-			<para>
-				CCRMA stands for "Center for Computer Research in Music and Acoustics," which is the name of an academic research initiative and music computing facility at Stanford University, located in Stanford, California.  Its initiatives help scholars to understand the effects and possibilities of computers and technology in various musical contexts.  They offer academic courses, hold workshops and concerts, and try to incorporate the work of many highly-specialized fields.
-			</para>
-		<!-- </section>
-		<section id="sect-Musicians_Guide-CCRMA_Software">
-			<title>The Software</title> -->
-			<para>
-				The Planet CCRMA at Home website suggests that they provide most of the software used on the computers in CCRMA's computing facilities.  Much of this software is highly advanced and complex, and not intended for everyday use.  More adventurous users are encouraged to explore Planet CCRMA's website, and investigate the software for themselves.
-			</para>
-		<!-- </section> -->
+		<para>
+			CCRMA stands for "Center for Computer Research in Music and Acoustics," which is the name of an academic research initiative and music computing facility at Stanford University, located in Stanford, California.  Its initiatives help scholars to understand the effects and possibilities of computers and technology in various musical contexts.  They offer academic courses, hold workshops and concerts, and try to incorporate the work of many highly-specialized fields.
+		</para>
+		<para>
+			The Planet CCRMA at Home website suggests that they provide most of the software used on the computers in CCRMA's computing facilities.  Much of this software is highly advanced and complex, and not intended for everyday use.  More adventurous users are encouraged to explore Planet CCRMA's website, and investigate the software for themselves.
+		</para>
 	</section>
 	
 	<section id="sect-Musicians_Guide-Knowing_Whether_to_Use_Planet_CCRMA">
@@ -35,11 +28,8 @@
 		<section id="sect-Musicians_Guide-CCRMA_Need_Exclusive_Software">
 			<title>Exclusive Software</title>
 			<para>
-				The only useful reason to install an additional repository is if you intend to install and use its software.  The only software application covered in this guide, which is available exclusively from the Planet CCRMA at Home repository, is "SuperCollider".  The Planet CCRMA repository also offers many other audio-related software applications, many of which are available from the default &O_S; Project repositories.
+				The only useful reason to install an additional repository is if you intend to install and use its software.  The only software application covered in this guide, which is available exclusively from the Planet CCRMA at Home repository, is "SuperCollider".  The Planet CCRMA repository also offers many other audio-related software applications, many of which are available from the default &OPERATING_SYSTEM; repositories.
 			</para>
-		<!-- </section>
-		<section id="sect-Musicians_Guide-CCRMA_Updated_Versions">
-			<title>Do You Need Updated Versions?</title> -->
 			<para>
 				Most of the audio software currently available in the default &O_S; repositories was initially available in &O_S; from the Planet CCRMA at Home repository.  Sometimes, an updated version of an application is available from the Planet CCRMA repository before it is available from the &O_S; Updates repository.  If you need the newer software version, then you should install the Planet CCRMA repository.
 			</para>
diff --git a/en-US/Qtractor.xml b/en-US/Qtractor.xml
index b46b6f5..bf74db5 100644
--- a/en-US/Qtractor.xml
+++ b/en-US/Qtractor.xml
@@ -175,7 +175,7 @@
 		</section>
 		
 		<section id="sect-Musicians_Guide-Qtractor-Using-MIDI_Tools">
-			<title>Using the MIDI Matrix Editor's Tools</title>
+			<title>Use the MIDI Matrix Editor's Tools</title>
 			<para>
 				Qtractor's matrix editor for MIDI clips offers a collection of useful tools, available from the "Tools" menu in the matrix editor window.  These tools only operate on MIDI notes selected in the matrix editor window before the tool window is opened.  Regardless of which tool you select from the menu, the same options are available to you each time the window is opened.  It is possible to use multiple tools at a time.
 			</para>
@@ -357,18 +357,18 @@ You can import <application>LilyPond</application> MIDI output in <application>Q
 			</para>
 		</section>
 		<section id="sect-Musicians_Guide-Qtractor-Tutorial-Getting_Qtractor_Ready">
-			<title>Get Qtractor Ready</title>
+			<title>Prepare <application>Qtractor</application></title>
 			<para>
 				<orderedlist>
-				<listitem><para>Open QjackCtl, and start JACK.</para></listitem>
-				<listitem><para>Open Qsynth, and configure it with one instance, using the default FluidR3 SoundFont.</para></listitem>
-				<listitem><para>Open Qtractor</para></listitem>
+				<listitem><para>Open <application>QjackCtl</application>, and start JACK.</para></listitem>
+				<listitem><para>Open <application>Qsynth</application>, and configure it with one instance, using the default FluidR3 SoundFont.</para></listitem>
+				<listitem><para>Open <application>Qtractor</application>.</para></listitem>
 				<listitem><para>Configure the MIDI tracks to cooperate with the default FluidR3 SoundFont.</para></listitem>
-				<listitem><para>Switch to QjackCtl and ensure the proper connections:
+				<listitem><para>Switch to <application>QjackCtl</application> and ensure the proper connections:
 					<itemizedlist>
-					<listitem><para>Qtractor's MIDI out (on "ALSA" page) is connected to Qsynth's MIDI in</para></listitem>
-					<listitem><para>Qsynth's audio out is connected to system in (the speakers)</para></listitem>
-					<listitem><para>Qtractor's audio out is conencted to system in (the speakers)</para></listitem>
+					<listitem><para>The <application>Qtractor</application> MIDI out (on "ALSA" page) is connected to the <application>Qsynth</application> MIDI in</para></listitem>
+					<listitem><para>The <application>Qsynth</application> audio out is connected to system in (the speakers)</para></listitem>
+					<listitem><para>The <application>Qtractor</application> audio out is conencted to system in (the speakers)</para></listitem>
 					<listitem><para>No other connections are necessary.</para></listitem>
 					</itemizedlist>
 				</para></listitem>
diff --git a/en-US/Revision_History.xml b/en-US/Revision_History.xml
index 9bd84f4..3225abe 100644
--- a/en-US/Revision_History.xml
+++ b/en-US/Revision_History.xml
@@ -408,13 +408,11 @@
 			
 			<!-- NOTE: When adding a revision above, be sure to update the <edition> tag in "Book_Info.xml" -->
 			
-			<!-- Fedora 16 -->
+			<!-- Fedora 17 (early 2012) -->
 			<!-- TODO: standardize the paragraph about installing JACK -->
 			<!-- TODO: Bug 710330 ("Section 11.5.1 Broken Link to Local Help File") -->
 			<!-- TODO: Bug 710334 ("Section 12.7 Needs to Be Rewritten") -->
 			<!-- TODO: Revise the LilyPond introductory chapters -->
-			
-			<!-- Fedora 17 (early 2012) -->
 			<!-- TODO: convert SuperCollider examples to <xi:include ... /> -->
 			<!-- TODO: convert LilyPond examples to <xi:include ... /> -->
 			<!-- TODO: add source-file and PDF/graphics examples to LilyPond-syntax.xml; already started for example at line 365 -->


More information about the docs-commits mailing list