svn commit: r44935 - head/en_US.ISO8859-1/articles/nanobsd
Benedict Reuschling
bcr at FreeBSD.org
Sat May 24 15:24:59 UTC 2014
Author: bcr
Date: Sat May 24 15:24:58 2014
New Revision: 44935
URL: http://svnweb.freebsd.org/changeset/doc/44935
Log:
Remove redundant markup and words around filename tags.
Sprinkle capitalizations over title tags to make igor happy.
Whitespace fixes will follow next.
Modified:
head/en_US.ISO8859-1/articles/nanobsd/article.xml
Modified: head/en_US.ISO8859-1/articles/nanobsd/article.xml
==============================================================================
--- head/en_US.ISO8859-1/articles/nanobsd/article.xml Sat May 24 15:13:09 2014 (r44934)
+++ head/en_US.ISO8859-1/articles/nanobsd/article.xml Sat May 24 15:24:58 2014 (r44935)
@@ -86,7 +86,7 @@
<title>NanoBSD Howto</title>
<sect2 xml:id="design">
- <title>The design of NanoBSD</title>
+ <title>The Design of NanoBSD</title>
<para>Once the image is present on the medium, it is possible to
boot <application>NanoBSD</application>. The mass storage
@@ -121,7 +121,7 @@
are expected to persist after the system restarts.</para>
<example>
- <title>Making persistent changes to <filename>/etc/resolv.conf</filename></title>
+ <title>Making Persistent Changes to <filename>/etc/resolv.conf</filename></title>
<screen>&prompt.root; <userinput>vi /etc/resolv.conf</userinput>
[...]
@@ -140,13 +140,13 @@
all times is not a good idea, especially if
the <application>NanoBSD</application> system runs off a mass
storage medium that may be adversely affected by a large number
- of writes to the partition (i.e. when the filesystem syncer
+ of writes to the partition (like when the filesystem syncer
flushes data to the system disks).</para>
</note>
</sect2>
<sect2>
- <title>Building a NanoBSD image</title>
+ <title>Building a NanoBSD Image</title>
<para>A <application>NanoBSD</application> image is built using a
simple <filename>nanobsd.sh</filename> shell script, which can
@@ -186,7 +186,7 @@
</sect2>
<sect2>
- <title>Customizing a NanoBSD image</title>
+ <title>Customizing a NanoBSD Image</title>
<para>This is probably the most important and most interesting
feature of <application>NanoBSD</application>. This is also
@@ -195,7 +195,7 @@
<para>Invocation of the following command will force the
<filename>nanobsd.sh</filename> to read its configuration from
- the <filename>myconf.nano</filename> file located in the current
+ <filename>myconf.nano</filename> located in the current
directory:</para>
<screen>&prompt.root; <userinput>sh nanobsd.sh -c myconf.nano</userinput></screen>
@@ -213,7 +213,7 @@
</itemizedlist>
<sect3>
- <title>Configuration options</title>
+ <title>Configuration Options</title>
<para>With configuration settings, it is possible to configure options
passed to both the <buildtarget>buildworld</buildtarget>
@@ -264,14 +264,14 @@
<listitem>
<para><literal>FlashDevice</literal> — Defines what type of
- media to use. Check the <filename>FlashDevice.sub</filename>
- file for more details.</para>
+ media to use. Check <filename>FlashDevice.sub</filename>
+ for more details.</para>
</listitem>
</itemizedlist>
</sect3>
<sect3>
- <title>Custom functions</title>
+ <title>Custom Functions</title>
<para>It is possible to fine-tune
<application>NanoBSD</application> using shell functions in
@@ -322,7 +322,7 @@ customize_cmd cust_etc_size</programlist
</sect3>
<sect3>
- <title>Adding packages</title>
+ <title>Adding Packages</title>
<para>Packages can be added to a <application>NanoBSD</application>
image using a custom function. The following function will install
@@ -339,7 +339,7 @@ customize_cmd install_packages</programl
</sect3>
<sect3>
- <title>Configuration file example</title>
+ <title>Configuration File Example</title>
<para>A complete example of a configuration file for building a
custom <application>NanoBSD</application> image can be:</para>
@@ -414,7 +414,7 @@ customize_cmd cust_nobeastie</programlis
<para>The most important difference of this step from the
initial <application>NanoBSD</application> installation is that
- now instead of using the <filename>_.disk.full</filename> file
+ now instead of using <filename>_.disk.full</filename>
(which contains an image of the entire disk),
the <filename>_.disk.image</filename> image is installed (which
contains an image of a single system partition).</para>
More information about the svn-doc-head
mailing list