From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS20473 45.76.80.0/20 X-Spam-Status: No, score=-3.3 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.6 Received: from mail.smrk.net (mail.smrk.net [45.76.87.244]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA512) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 6EC101F406 for ; Mon, 16 Oct 2023 22:16:22 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (2048-bit key; unprotected) header.d=smrk.net header.i=@smrk.net header.a=rsa-sha256 header.s=20221002 header.b=db47zpDx; dkim-atps=neutral DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=smrk.net; s=20221002; t=1697494579; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=xyHHw0nATGKGEN4FI6GcORYT27c4CbRvii1x6QEfKXY=; b=db47zpDxqiETVjqaL6BA0gcXWzrh70wf9k2F6WBJSRNtj95aie6rL2Z7HFbbICC4Mw/gfH Ccz9SdiT6v8I/xxlbipAsQ2xIzhycUKcLaQAv8axtv9r4KoYnDwDvJ9GhrJtuDzkPt5k+R CVHwrTuFuMroL26mr3wk9k6CWP+Q3EHs1V2eSgS4z/lz0qJTNPzCgZeWDFq2gt9KLYvgJN gAaNt6NATygv6hV/Slsos9CjsEi7Ns0s0tsQ4sTv94PRzsd6WFc8cIXwL/8/Hj+jo9ladN hZps693OYdElINTaf6qTM4PxXTD42DDZXjNzPlNtewBpOqHfRgDOt+xQUN4PXw== Received: from localhost ( [192.168.5.2]) by smrk (OpenSMTPD) with ESMTPSA id f18e0e46 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Tue, 17 Oct 2023 00:16:19 +0200 (CEST) From: =?utf-8?B?xaB0xJtww6FuIE7Em21lYw==?= To: Eric Wong Cc: meta@public-inbox.org Subject: Re: [PATCH 1/3] doc: fix some typos and grammar In-Reply-To: <20231016211320.M268439@dcvr> References: <20231016113304.2788497-1-stepnem@smrk.net> <20231016211320.M268439@dcvr> User-Agent: Notmuch/0.38 (https://notmuchmail.org) Emacs/30.0.50 (x86_64-pc-linux-gnu) Date: Tue, 17 Oct 2023 00:16:19 +0200 Message-ID: <20231017001619+0200.395012-stepnem@smrk.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: On Mon, 16 Oct 2023 21:13:20 +0000 Eric Wong wrote: >> --- a/TODO >> +++ b/TODO >> @@ -26,7 +26,7 @@ all need to be considered for everything we introduce.) >> archive locations to avoid SPOF. >>=20=20 >> * optional Cache::FastMmap support so production deployments won't >> - need Varnish (Varnish doesn't protect NNTP nor IMAP, either) >> + need Varnish (Varnish doesn't protect NNTP or IMAP, either) > > I'm not sure about this change, I seem to remember `nor' being > more suited for negatives. I'm about 100% sure about this :-P > Any citations or comments from others reading this? I'm sure you will find many explanations in books / guides / Internet, here's from one of the first DDG hits: https://grammarhow.com/or-vs-nor/ 1. When making a negative statement that doesn=E2=80=99t contain =E2=80=9Ceither=E2=80=9D or =E2=80=9Cneither=E2=80=9D, and the second ite= m is a noun, adjective, or adverb phrase, you should use =E2=80=9Cor=E2=80=9D instead = of =E2=80=9Cnor=E2=80=9D to continue the negation. He doesn=E2=80=99t like pizza or pasta.=20 He isn=E2=80=99t coming tonight or tomorrow because he is sick. He doesn=E2=80=99t speak English clearly or fluently. If you wanted a version with "nor", that would be "Varnish protects neither NNTP nor IMAP", but the meaning is slightly different. In short, you either use the n-words or the non-n-words (the two pairs don't mix), and if the verb itself is negated, you use either/or. >> Files in this directory are designed for: >>=20=20 >> -* users using from git or tarballs (and not the OS package manager) >> +* users using git repo or tarballs (and not the OS package manager) > > I wonder if: > > * users using our code from git or tarballs (and not the OS package man= ager) > > ...is better. I always feel the need to clarify git the software > vs. our code repo vs. our mirror on public-inbox.org/git *shrug* Yeah, I agree that's better. Maybe also change "using" to "running"? "Users using" is a bit awkward. Thank you for the date-related explanations, and the rediff tip! --=20 =C5=A0t=C4=9Bp=C3=A1n