summaryrefslogtreecommitdiffstats
path: root/bluez.tex
diff options
context:
space:
mode:
Diffstat (limited to 'bluez.tex')
-rw-r--r--bluez.tex8
1 files changed, 4 insertions, 4 deletions
diff --git a/bluez.tex b/bluez.tex
index e657076..2c39450 100644
--- a/bluez.tex
+++ b/bluez.tex
@@ -228,7 +228,7 @@ Currently, only the method "Just Works" is running (method provides no
protection against eavesdroppers or man in the middle attacks during the
pairing process).
-In BlueZ API, we have two methods to connect and/or pair with devices,
+In BlueZ API, there are two methods to connect and/or pair with devices,
{\em CreateDevice} and {\em CreatePairedDevice}.
{\em CreateDevice} creates a new object path for a remote device and
@@ -239,7 +239,7 @@ method will fail if a path for the remote device already exists.
It creates object path (if not exists), connect to remote device and then
initiate the pairing. It will fails if the pairing already exists.
-Consequently we have the option of create a device connection with
+Consequently there is the option of create a device connection with
{\em CreateDevice} and pair after with {\em CreatePairedDevice}.
Addtionally, we can increasing security level after connection setting
@@ -327,7 +327,7 @@ levels.
This profile is implemented in BlueZ and has a specific D-Bus API (described in
{\em doc/proximity-api.txt} located on BlueZ source code) for both roles.
-For Monitor role we have:
+For Monitor role there is:
\begin{enumerate}
\item Methods: GetProperties(), SetProperty()
\item Signals: PropertyChanged()
@@ -380,7 +380,7 @@ temperatures. {\em Device Information} \cite{dis} service is optional, but
{\em Thermometer} \cite{htp} profile is implemented in BlueZ and accessible via
D-Bus (described in {\em doc/thermometer-api.txt}).
-Under \verb|org.bluez.Thermometer| interface, we have:
+Under \verb|org.bluez.Thermometer| interface, there is:
\begin{enumerate}
\item Methods: SetProperty(), GetProperties(), RegisterWatcher(),
UnregisterWatcher(), EnableIntermediateMeasurement(),