Date: Thu, 4 Apr 2002 16:32:27 +0300 From: Giorgos Keramidas <keramida@FreeBSD.org> To: freebsd-doc@FreeBSD.org Subject: RFC: Removing "try and <verb>" from the docs Message-ID: <20020404133226.GA8872@hades.hell.gr>
index | next in thread | raw e-mail
[-- Attachment #1 --]
I've tried to remove "try and <verb>" from the English part of the
documentation. The patch below shows what changes I made. Since this
touches several files, I'd be glad to hear any comments or suggestions
you might have. If nobody objects to this, I'll try to have it
committed in a few days.
%%%
Index: en_US.ISO8859-1/articles/committers-guide/article.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/articles/committers-guide/article.sgml,v
retrieving revision 1.106
diff -u -r1.106 article.sgml
--- en_US.ISO8859-1/articles/committers-guide/article.sgml 27 Mar 2002 12:40:02 -0000 1.106
+++ en_US.ISO8859-1/articles/committers-guide/article.sgml 3 Apr 2002 22:10:59 -0000
@@ -1683,7 +1683,7 @@
course) but CVS makes it unnecessary to have an ongoing
dispute raging when it is far easier to simply reverse the
disputed change, get everyone calmed down again and then
- try and figure out how best to proceed. If the change
+ try to figure out what is the best way to proceed. If the change
turns out to be the best thing after all, it can be easily
brought back. If it turns out not to be, then the users
did not have to live with the bogus change in the tree
@@ -1740,7 +1740,7 @@
to continue to attract new members. There will be
occasions when, despite everyone's very best attempts at
self-control, tempers are lost and angry words are
- exchanged, and the best we can do is try and minimize the
+ exchanged. The best thing that can be done in such cases is to attempt to minimize the
effects of this until everyone has cooled back down. That
means that you should not air your angry words in public
and you should not forward private correspondence to
Index: en_US.ISO8859-1/articles/contributing/article.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/articles/contributing/article.sgml,v
retrieving revision 1.480
diff -u -r1.480 article.sgml
--- en_US.ISO8859-1/articles/contributing/article.sgml 27 Mar 2002 01:16:38 -0000 1.480
+++ en_US.ISO8859-1/articles/contributing/article.sgml 3 Apr 2002 22:11:27 -0000
@@ -89,7 +89,7 @@
<para>If you run FreeBSD-current and have a good Internet
connection, there is a machine <hostid
role="fqdn">current.FreeBSD.org</hostid> which builds a full
- release once a day — every now and again, try and install
+ release once a day — every now and again, try to install
the latest release from it and report any failures in the
process.</para>
</listitem>
Index: en_US.ISO8859-1/articles/cvs-freebsd/article.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/articles/cvs-freebsd/article.sgml,v
retrieving revision 1.1
diff -u -r1.1 article.sgml
--- en_US.ISO8859-1/articles/cvs-freebsd/article.sgml 7 Jan 2002 20:15:05 -0000 1.1
+++ en_US.ISO8859-1/articles/cvs-freebsd/article.sgml 3 Apr 2002 22:12:46 -0000
@@ -114,7 +114,7 @@
<para>Next, we will copy the FreeBSD <filename>CVSROOT</filename>
sources into your own repository. If you are accustomed to
- <application>CVS</application>, it might occur to you to try and
+ <application>CVS</application>, you might be thinking that you can just
import the scripts, in an attempt to make synchronizing with later
versions easier. However, it turns out that
<application>CVS</application> has a deficiency in this area:
Index: en_US.ISO8859-1/articles/filtering-bridges/article.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/articles/filtering-bridges/article.sgml,v
retrieving revision 1.8
diff -u -r1.8 article.sgml
--- en_US.ISO8859-1/articles/filtering-bridges/article.sgml 1 Apr 2002 23:42:04 -0000 1.8
+++ en_US.ISO8859-1/articles/filtering-bridges/article.sgml 3 Apr 2002 22:13:16 -0000
@@ -181,7 +181,7 @@
will not be activated and the firewall, being in 'open' mode, will not
avoid any operations.</para>
- <para>If there are any problems, you should try and sort them out now
+ <para>If there are any problems, you should try to sort them out now
before proceeding.</para>
</sect1>
@@ -322,7 +322,7 @@
<para>That is, drop packets that are coming in from the outside claiming
to be from our network. This is something that you would commonly do to
- be sure that someone does not try and evade the packet filter, by
+ be sure that someone does not try to evade the packet filter, by
generating nefarious packets that look like they are from the inside.
The problem with that is that there is <emphasis>at least</emphasis> one
host on the outside interface that you do not want to ignore: the
Index: en_US.ISO8859-1/books/developers-handbook/policies/chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/developers-handbook/policies/chapter.sgml,v
retrieving revision 1.26
diff -u -r1.26 chapter.sgml
--- en_US.ISO8859-1/books/developers-handbook/policies/chapter.sgml 18 Feb 2002 01:57:39 -0000 1.26
+++ en_US.ISO8859-1/books/developers-handbook/policies/chapter.sgml 3 Apr 2002 22:14:08 -0000
@@ -38,7 +38,7 @@
to the maintainer for review before being committed. Only if the
maintainer does not respond for an unacceptable period of time, to
several emails, will it be acceptable to commit changes without review
- by the maintainer. However, it is suggested that you try and have the
+ by the maintainer. However, it is suggested that you try to have the
changes reviewed by someone else if at all possible.</para>
<para>It is of course not acceptable to add a person or group as
Index: en_US.ISO8859-1/books/developers-handbook/tools/chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/developers-handbook/tools/chapter.sgml,v
retrieving revision 1.18
diff -u -r1.18 chapter.sgml
--- en_US.ISO8859-1/books/developers-handbook/tools/chapter.sgml 27 Mar 2002 01:16:45 -0000 1.18
+++ en_US.ISO8859-1/books/developers-handbook/tools/chapter.sgml 3 Apr 2002 22:15:18 -0000
@@ -481,7 +481,7 @@
<listitem>
<para>Create an optimised version of the executable. The
- compiler performs various clever tricks to try and produce
+ compiler performs various clever tricks in an attempt to produce
an executable that runs faster than normal. You can add a
number after the <option>-O</option> to specify a higher
level of optimisation, but this often exposes bugs in the
@@ -1152,7 +1152,7 @@
so that the application can be installed in the correct
directory when it has been correctly compiled.</para>
- <para>This is a slightly confusing subject to try and explain.
+ <para>This is a slightly confusing subject to explain.
If you do not quite understand how <command>make</command>
works, the best thing to do is to write a simple program like
<quote>hello world</quote> and a make file like the one above
@@ -1721,8 +1721,8 @@
<para>Although Emacs does have menus, it is well worth learning
the key bindings, as it is much quicker when you are editing
- something to press a couple of keys than to try and find the
- mouse and then click on the right place. And, when you are
+ something to press a couple of keys than finding the
+ mouse and then clicking on the right place. And, when you are
talking to seasoned Emacs users, you will find they often
casually throw around expressions like <quote><literal>M-x
replace-s RET foo RET bar RET</literal></quote> so it is
Index: en_US.ISO8859-1/books/faq/book.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/faq/book.sgml,v
retrieving revision 1.423
diff -u -r1.423 book.sgml
--- en_US.ISO8859-1/books/faq/book.sgml 27 Mar 2002 01:16:46 -0000 1.423
+++ en_US.ISO8859-1/books/faq/book.sgml 4 Apr 2002 13:24:54 -0000
@@ -705,8 +705,14 @@
<listitem>
<para>The document's format. We produce the documentation in a
- number of different output formats to try and make it as
- flexible as possible. The current formats are;</para>
+ number of different output formats. Each format has its own
+ advantages and disadvantages. Some formats are better suited
+ for online reading, while others are beautiful when printed on
+ paper. Having the documentation available in any of these
+ formats ensures that our readers will be able to read the
+ parts they are interested in, either online on their monitor,
+ or after printing the documents on paper. The current formats
+ are:</para>
<informaltable frame="none">
<tgroup cols="2">
@@ -970,7 +976,7 @@
<para>Channel <literal>#FreeBSD</literal> on
<ulink URL="http://www.efnet.org/index.php">EFNet</ulink>;
is a FreeBSD forum, but do not go there for tech
- support or to try and get folks there to help you avoid
+ support or try to get folks there to help you avoid
the pain of reading man pages or doing your own research.
It is a chat channel, first and foremost, and topics there
are just as likely to involve sex, sports or nuclear
Index: en_US.ISO8859-1/books/fdp-primer/sgml-primer/chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/fdp-primer/sgml-primer/chapter.sgml,v
retrieving revision 1.30
diff -u -r1.30 chapter.sgml
--- en_US.ISO8859-1/books/fdp-primer/sgml-primer/chapter.sgml 27 Mar 2002 01:16:46 -0000 1.30
+++ en_US.ISO8859-1/books/fdp-primer/sgml-primer/chapter.sgml 3 Apr 2002 22:21:22 -0000
@@ -143,8 +143,8 @@
<para>This processing simply confirms that the choice of elements, their
ordering, and so on, conforms to that listed in the DTD. It does
<emphasis>not</emphasis> check that you have used
- <emphasis>appropriate</emphasis> markup for the content. If you were
- to try and mark up all the filenames in your document as function
+ <emphasis>appropriate</emphasis> markup for the content. If you
+ tried to mark up all the filenames in your document as function
names, the parser would not flag this as an error (assuming, of
course, that your DTD defines elements for filenames and functions,
and that they are allowed to appear in the same place).</para>
@@ -694,7 +694,7 @@
<sect3>
<title><filename>catalog</filename> files</title>
- <para>If you use the syntax above and try and process this document
+ <para>If you use the syntax above and process this document
using an SGML processor, the processor will need to have some way of
turning the FPI into the name of the file on your computer that
contains the DTD.</para>
Index: en_US.ISO8859-1/books/fdp-primer/structure/chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/fdp-primer/structure/chapter.sgml,v
retrieving revision 1.10
diff -u -r1.10 chapter.sgml
--- en_US.ISO8859-1/books/fdp-primer/structure/chapter.sgml 26 Mar 2002 22:31:55 -0000 1.10
+++ en_US.ISO8859-1/books/fdp-primer/structure/chapter.sgml 3 Apr 2002 22:22:35 -0000
@@ -242,7 +242,7 @@
separate directories prepares for future plans for the Handbook.
Specifically, it will soon be possible to include images in each
chapter. It makes more sense for each image to be stored in a
- directory with the text for the chapter than to try and keep the
+ directory with the text for the chapter than keeping the
text for all the chapters, and all the images, in one large
directory. Namespace collisions would be inevitable, and it is
easier to work with several directories with a few files in them
Index: en_US.ISO8859-1/books/fdp-primer/translations/chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/fdp-primer/translations/chapter.sgml,v
retrieving revision 1.17
diff -u -r1.17 chapter.sgml
--- en_US.ISO8859-1/books/fdp-primer/translations/chapter.sgml 15 Mar 2002 07:57:16 -0000 1.17
+++ en_US.ISO8859-1/books/fdp-primer/translations/chapter.sgml 3 Apr 2002 22:23:17 -0000
@@ -319,7 +319,7 @@
</orderedlist>
<para>If there are any problems then whoever is looking at the
- submission will get back to you to try and work them out.</para>
+ submission will get back to you to work them out.</para>
<para>If there are no problems your translation will be committed
as soon as possible.</para>
Index: en_US.ISO8859-1/books/handbook/basics/chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/basics/chapter.sgml,v
retrieving revision 1.59
diff -u -r1.59 chapter.sgml
--- en_US.ISO8859-1/books/handbook/basics/chapter.sgml 26 Mar 2002 23:37:38 -0000 1.59
+++ en_US.ISO8859-1/books/handbook/basics/chapter.sgml 3 Apr 2002 22:23:39 -0000
@@ -890,7 +890,7 @@
send—some of them have a specific meaning, others are interpreted
by the application, and the application's documentation will tell you
how that application interprets signals. You can only send a signal to
- a process that you own. If you try and send a signal to someone else's
+ a process that you own. If you send a signal to someone else's
process it will be ignored. The exception to this is the
<username>root</username> user, who can send signals to everyone's
processes.</para>
@@ -983,7 +983,7 @@
&prompt.root; <userinput>/bin/kill -s HUP 198</userinput></screen>
<para>In common most with Unix commands, &man.kill.1; will not print any
- output if it is successful. If you try and send a signal to a
+ output if it is successful. If you send a signal to a
process that you do not own then you will see <errorname>kill:
<replaceable>PID</replaceable>: Operation not
permitted</errorname>. If you mistype the PID you will either
Index: en_US.ISO8859-1/books/handbook/contrib/chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/contrib/chapter.sgml,v
retrieving revision 1.471
diff -u -r1.471 chapter.sgml
--- en_US.ISO8859-1/books/handbook/contrib/chapter.sgml 27 Mar 2002 01:16:48 -0000 1.471
+++ en_US.ISO8859-1/books/handbook/contrib/chapter.sgml 3 Apr 2002 22:23:56 -0000
@@ -74,7 +74,7 @@
<para>If you run FreeBSD-current and have a good Internet
connection, there is a machine <hostid
role="fqdn">current.FreeBSD.org</hostid> which builds a full
- release once a day — every now and again, try and install
+ release once a day — every now and again, try to install
the latest release from it and report any failures in the
process.</para>
</listitem>
Index: en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml,v
retrieving revision 1.117
diff -u -r1.117 chapter.sgml
--- en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml 1 Apr 2002 14:39:22 -0000 1.117
+++ en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml 3 Apr 2002 22:24:13 -0000
@@ -1048,7 +1048,7 @@
<screen>&prompt.root; <userinput>make -DNOPROFILE=true installworld</userinput></screen>
- <para>otherwise it would try and install profiled libraries that
+ <para>otherwise it would try to install profiled libraries that
had not been built during the <command>make buildworld</command>
phase.</para>
</note>
Index: en_US.ISO8859-1/books/handbook/introduction/chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/introduction/chapter.sgml,v
retrieving revision 1.64
diff -u -r1.64 chapter.sgml
--- en_US.ISO8859-1/books/handbook/introduction/chapter.sgml 15 Mar 2002 07:46:21 -0000 1.64
+++ en_US.ISO8859-1/books/handbook/introduction/chapter.sgml 3 Apr 2002 22:24:58 -0000
@@ -481,7 +481,7 @@
to that point suffering rather severely from almost a year's worth
of neglect. As the patchkit swelled ever more uncomfortably with
each passing day, we were in unanimous agreement that something
- had to be done and decided to try and assist Bill by providing
+ had to be done and decided to assist Bill by providing
this interim <quote>cleanup</quote> snapshot. Those plans came to
a rude halt when Bill Jolitz suddenly decided to withdraw his
sanction from the project without any clear indication of what
Index: en_US.ISO8859-1/books/handbook/policies/chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/policies/chapter.sgml,v
retrieving revision 1.25
diff -u -r1.25 chapter.sgml
--- en_US.ISO8859-1/books/handbook/policies/chapter.sgml 28 Feb 2002 03:47:08 -0000 1.25
+++ en_US.ISO8859-1/books/handbook/policies/chapter.sgml 3 Apr 2002 22:25:16 -0000
@@ -44,7 +44,7 @@
to the maintainer for review before being committed. Only if the
maintainer does not respond for an unacceptable period of time, to
several emails, will it be acceptable to commit changes without review
- by the maintainer. However, it is suggested that you try and have the
+ by the maintainer. However, it is suggested that you try to have the
changes reviewed by someone else if at all possible.</para>
<para>It is of course not acceptable to add a person or group as
%%%
Giorgos Keramidas FreeBSD Documentation Project
keramida@{freebsd.org,ceid.upatras.gr} http://www.FreeBSD.org/docproj/
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (FreeBSD)
iD8DBQE8rFXq1g+UGjGGA7YRAv41AJ9rDiuO1qqKKPnVEk6y2UuRE5GB1QCgw2ZZ
sbuBwnE3EOgOR6fKA8Sm0NY=
=N3Jb
-----END PGP SIGNATURE-----
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020404133226.GA8872>