From owner-freebsd-doc@FreeBSD.ORG Wed Jul 4 09:10:18 2007 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 13A0616A469 for ; Wed, 4 Jul 2007 09:10:18 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id BE2A013C483 for ; Wed, 4 Jul 2007 09:10:17 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l649AHaZ037510 for ; Wed, 4 Jul 2007 09:10:17 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l649AHSx037509; Wed, 4 Jul 2007 09:10:17 GMT (envelope-from gnats) Date: Wed, 4 Jul 2007 09:10:17 GMT Message-Id: <200707040910.l649AHSx037509@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: Marc Fonvieille Cc: Subject: Re: docs/114265: grammar and other nits in handbook/basics section X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Marc Fonvieille List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jul 2007 09:10:18 -0000 The following reply was made to PR docs/114265; it has been noted by GNATS. From: Marc Fonvieille To: Ben Kaduk Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: docs/114265: grammar and other nits in handbook/basics section Date: Wed, 4 Jul 2007 10:47:33 +0200 On Tue, Jul 03, 2007 at 07:12:15PM +0000, Ben Kaduk wrote: > > >Number: 114265 > >Category: docs > >Synopsis: grammar and other nits in handbook/basics section > >Confidential: no > >Severity: non-critical > >Priority: low > >Responsible: freebsd-doc > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: doc-bug > >Submitter-Id: current-users > >Arrival-Date: Tue Jul 03 19:20:00 GMT 2007 > >Closed-Date: > >Last-Modified: > >Originator: Ben Kaduk > >Release: 7.0-CURRENT > >Organization: > >Environment: > System: FreeBSD prolepsis.scs.uiuc.edu 7.0-CURRENT FreeBSD 7.0-CURRENT #1: Sun Apr 1 16:59:00 UTC 2007 kaduk@prolepsis.scs.uiuc.edu:/usr/obj/usr/src/sys/GENERIC i386 > >Description: > I attach a diff with many small changes in it; I'll take them in order. > > o groups-->group: either add an apostrophe to make it possessive or take it out; as is, it's wrong > > o an administrator-->that administrators: recommend is transitive > > o every other file system-->other file systems: you can mount filesystems on non-root filesystems, as described later. This change makes the text more correct . > > o grafted on the root file system-->...parent file system: same as previous > > o should-->must: in context, the requirement of FreeBSD is that you give a fully-qualified slice name, which includes the disk name. Out of context, someone else might not require this, but the first half of the sentence implies that we are telling the user how to talk to FreeBSD > > o three partitions-->three data partitions: no, it has four partitions -- three for data and one for swap. Make the text less confusing > > o [no PID collisions]: just seems like it might save some confusion > > o daemons et al: change punctuation for style/readibility; remove sentence fragment > > o BIND: actually is domain, not daemon, as discussed fairly recently on cvs-doc@ > > o signals: the current text implies that signals are the only way to communicate with daemons; however, I seem to recall that some daemons listen on local sockets for commands, or read named pipes > > o kill: punctuation correction > > o occur-->appear: occur implies action (to me, at least); appear is more passive > > o help-->help with: verb transitivity again > > o variable key-->variable/key: it's a pair, so punctuate it as such (I didn't do a build and I don't remember if the slash is a special character for sgml -- do you?) > > o colon separated-->colon-separated (twice): style? > [...] Hello, I cannot find any reference for this one, do you have some links about this usage? -- Marc