From: Pieter Venter <pietventer@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: Pieter Venter <pieterventer@gmail.com>
Subject: [PATCH BlueZ] doc: Fix grammar
Date: Thu, 19 Sep 2019 10:23:43 -0400 [thread overview]
Message-ID: <20190919142343.1416-1-pieterventer@gmail.com> (raw)
We don't use an before u, if it has a [j] sound.
---
doc/gatt-api.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/gatt-api.txt b/doc/gatt-api.txt
index 98fe7487c..9cceef9c0 100644
--- a/doc/gatt-api.txt
+++ b/doc/gatt-api.txt
@@ -13,7 +13,7 @@ Object Manager at its root that is solely responsible for the objects that
belong to that service.
Releasing a registered GATT service is not defined yet. Any API extension
-should avoid breaking the defined API, and if possible keep an unified GATT
+should avoid breaking the defined API, and if possible keep a unified GATT
remote and local services representation.
Service hierarchy
--
2.17.1
next reply other threads:[~2019-09-19 14:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 14:23 Pieter Venter [this message]
2019-09-19 20:19 [PATCH BlueZ] doc: Fix grammar Pieter Venter
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=20190919142343.1416-1-pieterventer@gmail.com \
--to=pietventer@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pieterventer@gmail.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;
as well as URLs for NNTP newsgroup(s).