From: Vyshnav Ajith <puthen1977@gmail.com>
To: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, corbet@lwn.net
Cc: netdev@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Vyshnav Ajith <puthen1977@gmail.com>
Subject: Slight improvement in readability
Date: Fri, 22 Nov 2024 04:16:04 +0530 [thread overview]
Message-ID: <20241121224604.12071-1-puthen1977@gmail.com> (raw)
Removed few extra spaces and changed from "a" to "an ISP"
Signed-off-by: Vyshnav Ajith <puthen1977@gmail.com>
---
Documentation/networking/eql.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/networking/eql.rst b/Documentation/networking/eql.rst
index a628c4c81166..4f47121323c9 100644
--- a/Documentation/networking/eql.rst
+++ b/Documentation/networking/eql.rst
@@ -23,9 +23,9 @@ EQL Driver: Serial IP Load Balancing HOWTO
Which is worse? A huge fee for a 56K leased line or two phone lines?
It's probably the former. If you find yourself craving more bandwidth,
- and have a ISP that is flexible, it is now possible to bind modems
+ and have an ISP that is flexible, it is now possible to bind modems
together to work as one point-to-point link to increase your
- bandwidth. All without having to have a special black box on either
+ bandwidth. All without having to have a special black box on either
side.
@@ -288,7 +288,7 @@ EQL Driver: Serial IP Load Balancing HOWTO
the load across two or more Cirrus chips.
The good news is that one gets nearly the full advantage of the
- second, third, and fourth line's bandwidth. (The bad news is
+ second, third, and fourth line's bandwidth. (The bad news is
that the connection establishment seemed fragile for the higher
speeds. Once established, the connection seemed robust enough.)
--
2.43.0
next reply other threads:[~2024-11-21 22:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-21 22:46 Vyshnav Ajith [this message]
2024-11-21 22:55 ` Slight improvement in readability Jonathan Corbet
2024-11-21 23:06 ` Matthew Wilcox
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=20241121224604.12071-1-puthen1977@gmail.com \
--to=puthen1977@gmail.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox