From owner-freebsd-doc Mon Dec 4 10:39:39 1995 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA22547 for doc-outgoing; Mon, 4 Dec 1995 10:39:39 -0800 Received: from fslg8.fsl.noaa.gov (fslg8.fsl.noaa.gov [137.75.131.171]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id KAA22538 for ; Mon, 4 Dec 1995 10:39:31 -0800 Received: by fslg8.fsl.noaa.gov (5.57/Ultrix3.0-C) id AA19594; Mon, 4 Dec 95 12:38:42 -0600 Received: by emu.fsl.noaa.gov (1.38.193.4/SMI-4.1 (1.38.193.4)) id AA28911; Mon, 4 Dec 1995 11:38:41 -0700 Date: Mon, 4 Dec 1995 11:38:41 -0700 From: kelly@fsl.noaa.gov (Sean Kelly) Message-Id: <9512041838.AA28911@emu.fsl.noaa.gov> To: charnier@lirmm.fr Cc: doc@freebsd.org In-Reply-To: <199512041615.RAA01646@lirmm.lirmm.fr> (charnier@lirmm.fr) Subject: Re: typos Sender: owner-doc@freebsd.org Precedence: bulk >>>>> "Philippe" == Philippe Charnier writes: Philippe> Here are some typos I found when reading the Philippe> handbook. A lot of these aren't necessarily typos but stylistic issues. For example, these colons you're suggesting in quite a few places might not be necessary. Some style guides say that colons are needed for complete sentences introducing a list, but aren't necessary for partial phrases that are completed by each list item. In this example, we need a colon: A number of alternatives exist, such as the following: * One alternative. * Another alternative. But not here: A number of alternatives exist, including * One alternative. * Another alternative. We should do what our style guide says ... as soon as we get one! -- Sean Kelly NOAA Forecast Systems Laboratory, Boulder Colorado USA I filled out an application that said, "In Case Of Emergency Notify". I wrote "Doctor"... What's my mother going to do? -- Steven Wright