[PATCH] Replace a few "literal" tags with "firstterm".

A number of early phrases that are currently tagged as "literal" are more properly (semantically) tagged as "firstterm". Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> --- this is just the first part of the re-tagging of literals to firstterms where appropriate. more submissions coming as i work my way further into the manual, but i'll at least try to do it a section at a time. Index: en/guide/users/concepts/filerole.xml =================================================================== --- en/guide/users/concepts/filerole.xml (revision 295576) +++ en/guide/users/concepts/filerole.xml (working copy) @@ -4,8 +4,8 @@ <info><title>File roles</title></info> <para> - Pyrus and The PEAR Installer categorize file types by their <literal>role</literal>. - A file role is equivalent to the web's concept of <literal>MIME type</literal>, + Pyrus and The PEAR Installer categorize file types by their <firstterm>role</firstterm>. + A file role is equivalent to the web's concept of <firstterm>MIME type</firstterm>, a concept that allows web browsers to determine how a file should be displayed or processed. A file role allows Pyrus and the PEAR Installer to determine where a file should be installed, the conditions under which the role can be Index: en/guide/users/concepts/maintainer.xml =================================================================== --- en/guide/users/concepts/maintainer.xml (revision 295576) +++ en/guide/users/concepts/maintainer.xml (working copy) @@ -4,9 +4,9 @@ <info><title>Maintainers and maintainer roles</title></info> <para> - PEAR and PEAR2 calls its developers <literal>maintainers</literal>, and + PEAR and PEAR2 call their developers <firstterm>maintainers</firstterm>, and classifies maintainers by their level of contribution to a package, or - their <literal>role</literal>. In addition, each maintainer must choose a + their <firstterm>role</firstterm>. In addition, each maintainer must choose a handle which can be used to refer to them in package.xml and in bug reports. A handle is an alphanumeric word with all lower-cased letters such as <literal>cellog</literal> @@ -15,8 +15,8 @@ to log into the website. </para> <para> - Developer roles are <literal>lead</literal>, <literal>developer</literal>, - <literal>contributor</literal> and <literal>helper</literal>. Only lead + Developer roles are <firstterm>lead</firstterm>, <firstterm>developer</firstterm>, + <firstterm>contributor</firstterm> and <firstterm>helper</firstterm>. Only lead maintainers have the permission to release a package. Both lead and developer maintainers may create and modify package roadmaps, and all developers can directly log into pear.php.net and change the status of Index: en/guide/users/concepts/package.xml =================================================================== --- en/guide/users/concepts/package.xml (revision 295576) +++ en/guide/users/concepts/package.xml (working copy) @@ -4,7 +4,7 @@ <para> The smallest unit that can be managed by Pyrus or the PEAR Installer is - a <literal>package</literal>. A package is a collection of files + a <firstterm>package</firstterm>. A package is a collection of files that are organized and defined by a meta-information file called <link linkend="guide.developers.package2.intro">package.xml</link>. </para> rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA Linux Consulting, Training and Kernel Pedantry. Web page: http://crashcourse.ca Twitter: http://twitter.com/rpjday ========================================================================