All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 422] Typing error in patches.rst in doc/guides/contributing at line 177
Date: Wed, 25 Mar 2020 08:17:23 +0000	[thread overview]
Message-ID: <bug-422-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=422

            Bug ID: 422
           Summary: Typing error in patches.rst in doc/guides/contributing
                    at line 177
           Product: DPDK
           Version: 20.02
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: doc
          Assignee: dev@dpdk.org
          Reporter: m.bilal@emumba.com
  Target Milestone: ---

File: doc/guides/contributing/patches.rst, line # 177:
"file as the code, rather than one big documentation patch at then end of a" 

The above line does not seem to make much sense, it is perhaps a typing error
i.e we should use "the" instead of "then" here. It should rather be:

"file as the code, rather than one big documentation patch at the end of a"

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2020-03-25  8:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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

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

  git send-email \
    --in-reply-to=bug-422-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@dpdk.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.