osmith submitted this change.

View Change

trx_toolkit/transceiver: Spellcheck

Noticed by Jenkins:

https: //gerrit.osmocom.org/c/osmocom-bb/+/39328/1/src/target/trx_toolkit/transceiver.py#134

Change-Id: Id2a59d6db53c7f90cd21a056da8b1ac4d85e0373
---
M src/target/trx_toolkit/transceiver.py
1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/src/target/trx_toolkit/transceiver.py b/src/target/trx_toolkit/transceiver.py
index e6af013..e3a457f 100644
--- a/src/target/trx_toolkit/transceiver.py
+++ b/src/target/trx_toolkit/transceiver.py
@@ -119,7 +119,7 @@
 	immediately.  Instead, they are being scheduled prematurely.
 
 	The rationale is that both transceiver and the L1 implementation
-	are separete processes that are not perfectly synchronized in time.
+	are separate processes that are not perfectly synchronized in time.
 	Moreover, the transceiver needs some time to prepare a burst for
 	transmission.  This is why the time difference between Uplink and
 	Downlink is actually much higher on practice (20 TDMA frame periods
@@ -131,7 +131,7 @@
 	the transmit queue until the appropriate time of transmission.
 
 	The API user is supposed to call recv_data_msg() in order to obtain
-	a L12TRX message on the TRXD (data) inteface, so it gets queued by
+	a L12TRX message on the TRXD (data) interface, so it gets queued by
 	this function.  Then, to ensure the timeous transmission, the user
 	of this implementation needs to call clck_tick() on each TDMA
 	frame.  Both functions are thread-safe (queue mutex).
@@ -288,7 +288,7 @@
 				"is not running => dropping..." % (self, msg.desc_hdr()))
 			return None
 
-		# Enque the message, it will be sent later
+		# Enqueue the message, it will be sent later
 		self.tx_queue_append(msg)
 		return msg
 

To view, visit change 39609. To unsubscribe, or for help writing mail filters, visit settings.