user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@yhbt.net>
To: meta@public-inbox.org
Cc: Leah Neukirchen <leah@vuxu.org>
Subject: [PATCH 3/4] doc/technical/whyperl: reword bit around installed docs
Date: Sun,  5 Jul 2020 22:44:51 +0000	[thread overview]
Message-ID: <20200705224452.6159-4-e@yhbt.net> (raw)
In-Reply-To: <20200705224452.6159-1-e@yhbt.net>

I originally proposed this rewording to address Leah's comment
but forgot to squash it in :x

Link: https://public-inbox.org/meta/20200408221741.GA10142@dcvr/
Cc: Leah Neukirchen <leah@vuxu.org>
---
 Documentation/technical/whyperl.txt | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/Documentation/technical/whyperl.txt b/Documentation/technical/whyperl.txt
index b0a0d16b..01ce71e2 100644
--- a/Documentation/technical/whyperl.txt
+++ b/Documentation/technical/whyperl.txt
@@ -26,9 +26,9 @@ Good Things
   have to waste bandwidth or space with giant toolchains or
   architecture-specific binaries.
 
-  Furthermore, Perl documentation is typically installed as
-  manpages, allowing users to quickly access and learn it
-  offline.
+  Furthermore, Perl documentation is typically installed
+  locally as manpages, allowing users to quickly refer
+  to documentation as needed.
 
 * Scripted, always editable by the end user
 

  parent reply	other threads:[~2020-07-05 22:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-05 22:44 [PATCH 0/4] a few minor doc updates Eric Wong
2020-07-05 22:44 ` [PATCH 1/4] git: use v5.10.1, parent.pm and Time::HiRes::stat Eric Wong
2020-07-05 22:44 ` [PATCH 2/4] doc: daemon: update documentation around Inline::C Eric Wong
2020-07-05 22:44 ` Eric Wong [this message]
2020-07-05 22:44 ` [PATCH 4/4] doc/technical/whyperl: note Perl 7 announcement Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200705224452.6159-4-e@yhbt.net \
    --to=e@yhbt.net \
    --cc=leah@vuxu.org \
    --cc=meta@public-inbox.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).