diff --git a/en_US.ISO8859-1/books/fdp-primer/doc-build/chapter.sgml b/en_US.ISO8859-1/books/fdp-primer/doc-build/chapter.sgml index f112fbcc69..e291fde802 100644 --- a/en_US.ISO8859-1/books/fdp-primer/doc-build/chapter.sgml +++ b/en_US.ISO8859-1/books/fdp-primer/doc-build/chapter.sgml @@ -309,7 +309,7 @@ PRI_LANG?= en_US.ISO8859-1 PRI_LANG in no way affects what documents - can, or even will, be built. It's main use is creating links to + can, or even will, be built. Its main use is creating links to commonly referenced documents into the FreeBSD documentation install root. @@ -378,7 +378,7 @@ PRI_LANG?= en_US.ISO8859-1 After that descriptive tuple, instructions on how to build the target may be given, if the conversion process between the - target and it's dependencies are not previously defined, or if + target and its dependencies are not previously defined, or if this particular conversion is not the same as the default conversion method. @@ -399,7 +399,7 @@ PRI_LANG?= en_US.ISO8859-1 What sets this macro apart from other targets? Basically, it is executed after the instructions given in the build procedure it is listed as a dependency to, - and it doesn't adjust .TARGET, which is the + and it does not adjust .TARGET, which is the variable which contains the name of the target currently being built. diff --git a/en_US.ISO8859-1/books/fdp-primer/sgml-markup/chapter.sgml b/en_US.ISO8859-1/books/fdp-primer/sgml-markup/chapter.sgml index a4881ed01a..e0d09af5bd 100644 --- a/en_US.ISO8859-1/books/fdp-primer/sgml-markup/chapter.sgml +++ b/en_US.ISO8859-1/books/fdp-primer/sgml-markup/chapter.sgml @@ -331,7 +331,7 @@ To: freebsd-doc@FreeBSD.org Subject: New documentation available - There's a new copy of my primer for contributers to the FreeBSD + There is a new copy of my primer for contributors to the FreeBSD Documentation Project available at @@ -1128,7 +1128,7 @@ In order to do this, use itemizedlist, orderedlist, or procedureThere are other types of - list element in DocBook, but we're not concerned with those at + list element in DocBook, but we are not concerned with those at the moment. @@ -1430,7 +1430,7 @@ main(void) - If you don't want a border around the table the + If you do not want a border around the table the frame attribute can be added to the informaltable element with a value of none (i.e., <informaltable @@ -2228,12 +2228,12 @@ This is the file called 'foo2' Image support in the documentation is currently extremely experimental. I think the mechanisms described here are unlikely to - change, but that's not guaranteed. + change, but that is not guaranteed. You will also need to install the graphics/ImageMagick port, which is used to convert between the different image formats. This is a big port, - and most of it is not required. However, while we're working on the + and most of it is not required. However, while we are working on the Makefiles and other infrastructure it makes things easier. This port is not in the textproc/docproj meta port, you must install it @@ -2241,7 +2241,7 @@ This is the file called 'foo2' The best example of what follows in practice is the doc/en_US.ISO8859-1/articles/vm-design/ document. - If you're unsure of the description that follows, take a look at the + If you are unsure of the description that follows, take a look at the files in that directory to see how everything hangs together. Experiment with creating different formatted versions of the document to see how the image markup appears in the formatted @@ -2512,7 +2512,7 @@ IMAGES= chapter1/fig1.png <sgmltag>anchor</sgmltag> This paragraph has an embedded - link target in it. It won't show up in + link target in it. It will not show up in the document.]]> diff --git a/en_US.ISO8859-1/books/fdp-primer/sgml-primer/chapter.sgml b/en_US.ISO8859-1/books/fdp-primer/sgml-primer/chapter.sgml index b966912874..360d269144 100644 --- a/en_US.ISO8859-1/books/fdp-primer/sgml-primer/chapter.sgml +++ b/en_US.ISO8859-1/books/fdp-primer/sgml-primer/chapter.sgml @@ -315,7 +315,7 @@ Single quotes around attributes - I'm on the right!

]]> + I am on the right!

]]> Sometimes you do not need to use quotes around attribute values at @@ -592,8 +592,8 @@ nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished - You don't need to know this, but it's useful background, and - might help you debug problems when your SGML processor can't locate + You do not need to know this, but it is useful background, and + might help you debug problems when your SGML processor can not locate the DTD you are using. @@ -633,7 +633,7 @@ nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished to assign registered names. The ISO council delegated this to the American National Standards Institute (ANSI). - Because the FreeBSD Project hasn't been registered the + Because the FreeBSD Project has not been registered the owner string is -//FreeBSD. And as you can see, the W3C are not a registered owner either. @@ -756,7 +756,7 @@ nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished typically (but not always) means the DTD will be provided as a filename. - Using FPIs is preferred for reasons of portability. You don't + Using FPIs is preferred for reasons of portability. You do not want to have to ship a copy of the DTD around with your document, and if you used the SYSTEM identifier then everyone would need to keep their DTDs in the same place. @@ -1038,7 +1038,7 @@ nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished (you may need to copy it to example.html before your browser recognises it as an HTML document). - Unless your browser is very advanced, you won't see the entity + Unless your browser is very advanced, you will not see the entity reference &version; replaced with the version number. Most web browsers have very simplistic parsers which do not handle proper SGML @@ -1394,7 +1394,7 @@ nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished <programlisting> <![ CDATA [ This is a sample that shows you some of the elements within - HTML. Since the angle brackets are used so many times, it's + HTML. Since the angle brackets are used so many times, it is simpler to say the whole example is a CDATA marked section than to use the entity names for the left and right angle brackets throughout.

@@ -1436,7 +1436,7 @@ nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished ]]> - By itself, this isn't too useful. If you wanted to remove text + By itself, this is not too useful. If you wanted to remove text from your document you could cut it out, or wrap it in comments. @@ -1448,10 +1448,10 @@ nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished For example, suppose that you produced a hard-copy version of some documentation and an electronic version. In the electronic - version you wanted to include some extra content that wasn't to + version you wanted to include some extra content that was not to appear in the hard-copy. - Create a parameter entity, and set it's value to + Create a parameter entity, and set its value to INCLUDE. Write your document, using marked sections to delimit content that should only appear in the electronic version. In these marked sections use the parameter diff --git a/en_US.ISO8859-1/books/fdp-primer/translations/chapter.sgml b/en_US.ISO8859-1/books/fdp-primer/translations/chapter.sgml index 43e1f0b044..269a9ce778 100644 --- a/en_US.ISO8859-1/books/fdp-primer/translations/chapter.sgml +++ b/en_US.ISO8859-1/books/fdp-primer/translations/chapter.sgml @@ -158,7 +158,7 @@ versions of the files that make up the documentation. [XXX To Do -- write a tutorial that shows how to use CVSup to - get just the documentation, check it out, and see what's changed + get just the documentation, check it out, and see what has changed between two arbitrary revisions] @@ -174,14 +174,14 @@ url="../../../../docproj/translations.html">Documentation Project translations page lists the translation efforts that are currently known about. If others are already working - on translating documentation to your language, please don't + on translating documentation to your language, please do not duplicate their efforts. Instead, contact them to see how you can help. If no one is listed on that page as translating for your language, then send a message to freebsd-doc@FreeBSD.org in case someone else is - thinking of doing a translation, but hasn't announced it yet. + thinking of doing a translation, but has not announced it yet. @@ -195,7 +195,7 @@ your-language-here Documentation Translation Project. Welcome aboard. - First, decide whether or not you've got the time to spare. Since + First, decide whether or not you have got the time to spare. Since you are the only person working on your language at the moment it is going to be your responsibility to publicise your work and coordinate any volunteers that might want to help you. @@ -221,7 +221,7 @@ - I've translated some documentation, where do I send it? + I have translated some documentation, where do I send it? @@ -239,12 +239,12 @@ - I'm the only person working on translating to this language, how + I am the only person working on translating to this language, how do I submit my translation? or - We're a translation team, and want to submit documentation that + We are a translation team, and want to submit documentation that our members have translated for us? @@ -342,7 +342,7 @@ Korean, and want to include a section about retailers in Korea in your Handbook. - There's no real reason why that information should not be in the + There is no real reason why that information should not be in the English (or German, or Spanish, or Japanese, or …) versions as well. It is feasible that an English speaker in Korea might try and pick up a copy of FreeBSD whilst over there. It also helps diff --git a/en_US.ISO8859-1/books/fdp-primer/writing-style/chapter.sgml b/en_US.ISO8859-1/books/fdp-primer/writing-style/chapter.sgml index bd94405b39..0e97435d4b 100644 --- a/en_US.ISO8859-1/books/fdp-primer/writing-style/chapter.sgml +++ b/en_US.ISO8859-1/books/fdp-primer/writing-style/chapter.sgml @@ -147,7 +147,7 @@ a period denotes a new sentence, this is not the case, especially in name usage. Jordan K. Hubbard is a good example; it has a capital H following a - period and a space, and there certainly isn't a new sentence + period and a space, and there certainly is not a new sentence there. @@ -269,12 +269,12 @@ V Separating tags Tags like itemizedlist which will - always have further tags inside them, and in fact don't take + always have further tags inside them, and in fact do not take character data themselves, are always on a line by themselves. Tags like para and - term don't need other tags to contain + term do not need other tags to contain normal character data, and their contents begin immediately after the tag, on the same line.