Diff between 87fb2b7b5a8068f9159c935951afb2c9f508a9d8 and cb8facbd9a54a9530ab51f03593ee793998c8db9

Changed Files

File Additions Deletions Status
doc/intel-variants.txt +1 -1 modified
doc/maintainer-guidelines.txt +1 -1 modified
doc/mesh-api.txt +7 -7 modified
doc/mgmt.rst +3 -3 modified
doc/org.bluez.Adapter.rst +2 -2 modified
doc/org.bluez.AdvertisementMonitor.rst +1 -1 modified
doc/org.bluez.DeviceSet.rst +2 -2 modified
doc/org.bluez.GattCharacteristic.rst +2 -2 modified
doc/org.bluez.MediaTransport.rst +1 -1 modified
doc/settings-storage.txt +1 -1 modified
doc/test-runner.rst +2 -2 modified

Full Patch

diff --git a/doc/intel-variants.txt b/doc/intel-variants.txt
index 4f51ca9..a9b27c6 100644
--- a/doc/intel-variants.txt
+++ b/doc/intel-variants.txt
@@ -1,4 +1,4 @@
-Intel Hardware Varaints
+Intel Hardware Variants
 =======================
 
 These are the list of Intel Bluetooth devices and its information.
diff --git a/doc/maintainer-guidelines.txt b/doc/maintainer-guidelines.txt
index 21162d4..b875f00 100644
--- a/doc/maintainer-guidelines.txt
+++ b/doc/maintainer-guidelines.txt
@@ -96,7 +96,7 @@ Rule 4: Pay extra attention to adding new files to the tree
 New files that are added to the tree require several things to be
 verified first:
 
-	- Check that the names are acceptible with other maintainers
+	- Check that the names are acceptable with other maintainers
 	- Ensure that the file modes are correct
 	- Verify that the license & copyright headers are correct
 	- If the file is supposed to be part of the release tarball,
diff --git a/doc/mesh-api.txt b/doc/mesh-api.txt
index c67b841..ff302c8 100644
--- a/doc/mesh-api.txt
+++ b/doc/mesh-api.txt
@@ -259,7 +259,7 @@ Methods:
 				message as one-segment payload. If not present,
 				the default setting is "false".
 
-		The data parameter is an outgoing message to be encypted by the
+		The data parameter is an outgoing message to be encrypted by the
 		bluetooth-meshd daemon and sent on.
 
 		Possible errors:
@@ -298,7 +298,7 @@ Methods:
 				message as one-segment payload. If not present,
 				the default setting is "false".
 
-		The data parameter is an outgoing message to be encypted by the
+		The data parameter is an outgoing message to be encrypted by the
 		meshd daemon and sent on.
 
 		Possible errors:
@@ -392,7 +392,7 @@ Methods:
 				Bluetooth SIG. This key should only exist when
 				publishing on a Vendor defined model.
 
-		The data parameter is an outgoing message to be encypted by the
+		The data parameter is an outgoing message to be encrypted by the
 		meshd daemon and sent on.
 
 		Since only one Publish record may exist per element-model, the
@@ -759,7 +759,7 @@ Methods:
 		assigned to this remote node.
 
 		The device_key parameter is the access layer key that will be
-		will used to decrypt privledged messages from this remote node.
+		will used to decrypt privileged messages from this remote node.
 
 		This call affects the local bluetooth-meshd key database only.
 
@@ -1109,7 +1109,7 @@ Object path	freely definable
 		unprovsioned devices.
 
 		The rssi parameter is a signed, normalized measurement of the
-		signal strength of the recieved unprovisioned beacon.
+		signal strength of the received unprovisioned beacon.
 
 		The data parameter is a variable length byte array, that may
 		have 1, 2 or 3 distinct fields contained in it including the 16
@@ -1131,8 +1131,8 @@ Object path	freely definable
 			received data will be returned here.
 
 		If a beacon with a UUID that has already been reported is
-		recieved by the daemon, it will be silently discarded unless it
-		was recieved at a higher rssi power level.
+		received by the daemon, it will be silently discarded unless it
+		was received at a higher rssi power level.
 
 
 	uint16 net_index, uint16 unicast RequestProvData(uint8 count)
diff --git a/doc/mgmt.rst b/doc/mgmt.rst
index bf7948d..5ffc766 100644
--- a/doc/mgmt.rst
+++ b/doc/mgmt.rst
@@ -4026,7 +4026,7 @@ The Window/Period values are used to set the Scan Parameters when no other
 scanning is being done.
 
 Num AD Types and AD Types parameter, filter Advertising and Scan responses by AD
-type. Reponses that do not contain at least one of the requested AD types will
+type. Responses that do not contain at least one of the requested AD types will
 be ignored. Otherwise they will be delivered with the Mesh Device Found event.
 
 Possible errors:
@@ -4080,7 +4080,7 @@ Transmit Mesh Packet (since 1.21)
 
 This command sends a Mesh Packet as a NONCONN LE Advertisement.
 
-The Addr + Addr Type parameters specifify the address to use in the outbound
+The Addr + Addr Type parameters specify the address to use in the outbound
 advertising packet. If BD_ADDR_ANY and LE_RANDOM is set, the kernel will create
 a single use non-resolvable address.
 
@@ -5367,7 +5367,7 @@ The RSSI field is a signed octet, and is the RSSI reported by the receiving
 controller.
 
 The Instant field is 64 bit value that represents the instant in time the packet
-was received. It's value is not intended to be interpretted by the host, and is
+was received. It's value is not intended to be interpreted by the host, and is
 only useful if the host wants to make a timed response to the received packet
 (i.e. a Poll/Response).
 
diff --git a/doc/org.bluez.Adapter.rst b/doc/org.bluez.Adapter.rst
index 174b604..41d6517 100644
--- a/doc/org.bluez.Adapter.rst
+++ b/doc/org.bluez.Adapter.rst
@@ -59,7 +59,7 @@ Possible errors:
 void RemoveDevice(object device)
 ````````````````````````````````
 
-Removes the remote device object at the given path including cahed information
+Removes the remote device object at the given path including cached information
 such as bonding information.
 
 Possible errors:
@@ -129,7 +129,7 @@ Possible filter values:
 	Disables duplicate detection of advertisement data.
 
 	When enabled PropertiesChanged signals will be generated for either
-	ManufacturerData and ServiceData everytime they are discovered.
+	ManufacturerData and ServiceData every time they are discovered.
 
 :bool Discoverable (Default false):
 
diff --git a/doc/org.bluez.AdvertisementMonitor.rst b/doc/org.bluez.AdvertisementMonitor.rst
index 33cdf79..e08bf41 100644
--- a/doc/org.bluez.AdvertisementMonitor.rst
+++ b/doc/org.bluez.AdvertisementMonitor.rst
@@ -142,7 +142,7 @@ The structure of a pattern contains the following:
 
 :uint8 start_position:
 
-	The index in an AD data field where the search hould start. The
+	The index in an AD data field where the search should start. The
 	beginning of an AD data field is index 0.
 
 :uint8 AD_data_type:
diff --git a/doc/org.bluez.DeviceSet.rst b/doc/org.bluez.DeviceSet.rst
index 47f2ac6..fa277bd 100644
--- a/doc/org.bluez.DeviceSet.rst
+++ b/doc/org.bluez.DeviceSet.rst
@@ -25,7 +25,7 @@ void Connect() [experimental]
 `````````````````````````````
 
 Connects all **devices** members of the set, each member is connected in
-sequence as they were added/loaded following the same proceedure as described in
+sequence as they were added/loaded following the same procedure as described in
 **Device1.Connect**.
 
 Possible errors:
@@ -39,7 +39,7 @@ void Disconnect() [experimental]
 ````````````````````````````````
 
 Disconnects all **devices** members of the set, each member is disconnected in
-sequence as they were connected following the same proceedure as described in
+sequence as they were connected following the same procedure as described in
 **Device1.Disconnect**.
 
 Possible errors:
diff --git a/doc/org.bluez.GattCharacteristic.rst b/doc/org.bluez.GattCharacteristic.rst
index 245f4ba..3cbf361 100644
--- a/doc/org.bluez.GattCharacteristic.rst
+++ b/doc/org.bluez.GattCharacteristic.rst
@@ -303,7 +303,7 @@ boolean WriteAcquired [read-only, optional]
 
 True, if this characteristic has been acquired by any client using AcquireWrite.
 
-For client properties is ommited in case 'write-without-response' flag is not
+For client properties is omitted in case 'write-without-response' flag is not
 set.
 
 For server the presence of this property indicates that AcquireWrite is
@@ -315,7 +315,7 @@ boolean NotifyAcquired [read-only, optional]
 True, if this characteristic has been acquired by any client using
 AcquireNotify.
 
-For client this properties is ommited in case 'notify' flag is not set.
+For client this properties is omitted in case 'notify' flag is not set.
 
 For server the presence of this property indicates that AcquireNotify is
 supported.
diff --git a/doc/org.bluez.MediaTransport.rst b/doc/org.bluez.MediaTransport.rst
index 2f9e5e1..3d1e8c5 100644
--- a/doc/org.bluez.MediaTransport.rst
+++ b/doc/org.bluez.MediaTransport.rst
@@ -166,7 +166,7 @@ For a Broadcast Sink, the BIG sync procedure requires all desired streams to be
 enumerated from the start and it cannot be later reconfigured by adding or
 removing BISes.
 
-To avoid terminating and recreating the BIG sync everytime a new transport is
+To avoid terminating and recreating the BIG sync every time a new transport is
 selected for acquire, all transports selected via **Select** need to be linked
 together.
 
diff --git a/doc/settings-storage.txt b/doc/settings-storage.txt
index fe862c7..0a2cc70 100644
--- a/doc/settings-storage.txt
+++ b/doc/settings-storage.txt
@@ -107,7 +107,7 @@ Sample:
 Identity file format
 ====================
 Identity file contains one [General] group that holds identity information
-such as keys and adresses:
+such as keys and addresses:
 
 	IdentityResolvingKey	String	128-bit value of the IRK
 
diff --git a/doc/test-runner.rst b/doc/test-runner.rst
index 1b4eeb9..cb56d5b 100644
--- a/doc/test-runner.rst
+++ b/doc/test-runner.rst
@@ -92,8 +92,8 @@ Bluetooth
 
 	CONFIG_UHID=y
 
-Lock debuging
--------------
+Lock debugging
+--------------
 
 To catch locking related issues the following set of kernel config
 options may be useful: