From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: [PATCH] Documentation: Minor editing changes to filesystems content.
Date: Sat, 28 Jun 2014 06:22:39 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1406280621410.30555@localhost> (raw)
Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
---
diff --git a/Documentation/filesystems/nfs.rst b/Documentation/filesystems/nfs.rst
index b8ad4f3..f4eda5d 100644
--- a/Documentation/filesystems/nfs.rst
+++ b/Documentation/filesystems/nfs.rst
@@ -5,7 +5,7 @@
NFS Support
===========
-barebox has readonly support for NFSv3 un UDP mode.
+barebox has readonly support for NFSv3 in UDP mode.
Example::
diff --git a/Documentation/filesystems/ramfs.rst b/Documentation/filesystems/ramfs.rst
index 70e7282..b7ece1a 100644
--- a/Documentation/filesystems/ramfs.rst
+++ b/Documentation/filesystems/ramfs.rst
@@ -3,10 +3,10 @@
RAM filesystem
==============
-ramfs is a simple malloc based filesystem. An instance of ramfs is
-mounted during startup on /. The filesystem type passed to mount is
-'ramfs'
+ramfs is a simple malloc-based filesystem. An instance of ramfs is
+mounted during startup on /. The filesystem type passed to ``mount``
+is ``ramfs``.
-example::
+Example::
mount none ramfs /somedir
diff --git a/Documentation/filesystems/tftp.rst b/Documentation/filesystems/tftp.rst
index 273be5e..e0a1159 100644
--- a/Documentation/filesystems/tftp.rst
+++ b/Documentation/filesystems/tftp.rst
@@ -8,8 +8,8 @@ TFTP support
barebox has read/write support for the Trivial File Transfer Protocol.
TFTP is not designed as a filesystem. It does not have support for listing
-directories. This means a :ref:`command_ls` to a TFTP mounted path will show an empty
-directory. Nevertheless the files are there.
+directories. This means a :ref:`command_ls` to a TFTP-mounted path will show an empty
+directory. Nevertheless, the files are there.
Example::
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2014-06-28 10:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-28 10:22 Robert P. J. Day [this message]
2014-06-30 6:13 ` [PATCH] Documentation: Minor editing changes to filesystems content Sascha Hauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.11.1406280621410.30555@localhost \
--to=rpjday@crashcourse.ca \
--cc=barebox@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.