Hello,
I fixed typos in the osmo-gsm-manuals repository.
This is my first contribution to the Osmocom project so I'm not quite sure if I did all the things (patch, email) in the right way.
Best Regards
Jonathan Brielmaier
---
OsmoBSC/chapters/alink.adoc | 4 ++--
OsmoBSC/chapters/overview.adoc | 4 ++--
OsmoBTS/abis/rsl.adoc | 4 ++--
OsmoBTS/chapters/architecture.adoc | 2 +-
OsmoBTS/chapters/bts-models.adoc | 10 +++++-----
OsmoBTS/chapters/interfaces.adoc | 2 +-
OsmoBTS/osmobts-abis.adoc | 2 +-
OsmoNITB/chapters/mncc.adoc | 2 +-
OsmoNITB/chapters/net.adoc | 2 +-
OsmoNITB/chapters/running.adoc | 4 ++--
OsmoNITB/chapters/smpp.adoc | 2 +-
OsmoPCU/chapters/configuration.adoc | 6 +++---
OsmoPCU/chapters/overview.adoc | 2 +-
OsmoPCU/osmopcu-gb.adoc | 2 +-
OsmoSGSN/chapters/configuration.adoc | 2 +-
OsmoSGSN/chapters/gsup.adoc | 4 ++--
common/chapters/gb.adoc | 2 +-
common/chapters/glossary.adoc | 10 +++++-----
common/chapters/preface.adoc | 10 +++++-----
common/chapters/vty.adoc | 8 ++++----
20 files changed, 42 insertions(+), 42 deletions(-)
diff --git a/OsmoBSC/chapters/alink.adoc b/OsmoBSC/chapters/alink.adoc
index 37e64c0..081e03f 100644
--- a/OsmoBSC/chapters/alink.adoc
+++ b/OsmoBSC/chapters/alink.adoc
@@ -3,12 +3,12 @@
OsmoBSC implements a minimal sub-set of the GSM A interface as specified
in TS 08.08.
-Unlike classic A interface implementations for E1 interfacs, OsmoBSC
+Unlike classic A interface implementations for E1 interface, OsmoBSC
implements a variant of encapsulating the A interface over IP. To do
so, the SCCP messages are wrapped in an IPA multiplex and then
communicated over TCP. The audio channels are mapped to RTP streams.
-This protcol stacking is sometimes called "SCCPlite".
+This protocol stacking is sometimes called "SCCPlite".
===
diff --git a/OsmoBSC/chapters/overview.adoc b/OsmoBSC/chapters/overview.adoc
index 6577df8..580a42e 100644
--- a/OsmoBSC/chapters/overview.adoc
+++ b/OsmoBSC/chapters/overview.adoc
@@ -9,7 +9,7 @@ aspects of configuring and running the OsmoBSC.
OsmoBSC is one particular version of the OpenBSC software suite.
-Unlike the highly integrated OmsoNITB, OsmoBSC impleents a more classic
+Unlike the highly integrated OmsoNITB, OsmoBSC implements a more classic
GSM Base Station Controller with A-bis interface towards BTSs and A
interface towards a MSC.
@@ -39,7 +39,7 @@ implements a variant of encapsulating the A interface over IP. To do
so, the SCCP messages are wrapped in an IPA multiplex and then
communicated over TCP. The audio channels are mapped to RTP streams.
-This protcol stacking is sometimes called "SCCPlite".
+This protocol stacking is sometimes called "SCCPlite".
For more information, see <<alink>>.
diff --git a/OsmoBTS/abis/rsl.adoc b/OsmoBTS/abis/rsl.adoc
index f32fb94..331ccb3 100644
--- a/OsmoBTS/abis/rsl.adoc
+++ b/OsmoBTS/abis/rsl.adoc
@@ -91,7 +91,7 @@ Specific limitations apply, see the linked sections.
| 8.4.24 | ROUND TRIP DELAY REPORT
| 8.4.25 | PRE-HANDOVER NOTIFICATION
| 8.4.26 | MULTIRATE CODEC MODIFICATION REQUEST
-| 8.4.27 | MULTIRATE CODEC MODIFICATION ACKNOLEWDGE
+| 8.4.27 | MULTIRATE CODEC MODIFICATION ACKNOWLEDGE
| 8.4.28 | MULTIRATE CODEC MODIFICATION NEGATIVE ACKNOWLEDGE
| 8.4.29 | MULTIRATE CODEC MODIFICATION PERFORMED
| 8.4.30 | TFO REPORT
@@ -115,7 +115,7 @@ Specific limitations apply, see the linked sections.
Conforms to 3GPP TS 08.58 § 8.4.8 with this limitation:
-._Measuremet Result_ IE limitations
+._Measurement Result_ IE limitations
[options="header",cols="10%,30%,60%"]
|===
| TS 08.58 § | IE Name | Handling
diff --git a/OsmoBTS/chapters/architecture.adoc b/OsmoBTS/chapters/architecture.adoc
index aca5bb9..a0e66cd 100644
--- a/OsmoBTS/chapters/architecture.adoc
+++ b/OsmoBTS/chapters/architecture.adoc
@@ -83,7 +83,7 @@ order to specify which PHY instance is allocated to this specific TRX.
| common | bts_controlif_setup() | Initialization of Control Interface
| bts-specific | bts_model_ctrl_cmds_install() | Install model-specific control interface commands
| common | telnet_init() | Initialization of telnet interface
-| common | pcu_sock_init() | Initializaiton of PCU socket
+| common | pcu_sock_init() | Initialization of PCU socket
| common | main() | Installation of signal handlers
| common | abis_open() | Start of the A-bis connection to BSC
| common | phy_links_open() | Iterate over list of configured PHY links
diff --git a/OsmoBTS/chapters/bts-models.adoc b/OsmoBTS/chapters/bts-models.adoc
index 5a967f6..a4c65d2 100644
--- a/OsmoBTS/chapters/bts-models.adoc
+++ b/OsmoBTS/chapters/bts-models.adoc
@@ -33,10 +33,10 @@ Each bts_model may offer
== `osmo-bts-sysmo` for sysmocom sysmoBTS
-The sysmocom sysmoBTS is a range of GSM BTSs basd around an embedded
+The sysmocom sysmoBTS is a range of GSM BTSs based around an embedded
system implementing the PHY in a combination of DSP+FPGA. The PHY is
configured by a set of primitives described by header files. Those
-primitives are exchanged ove a set of message queues exposed on the
+primitives are exchanged over a set of message queues exposed on the
Linux-running ARM core via device nodes in `/dev/msgq/`. Internally,
the message queues map to shared memory between the Linux-running ARM
core and the DSP running the PHY implementation.
@@ -62,7 +62,7 @@ vice-versa.
<<osmo-bts-sysmo-dsp-trace>> for further information.
*--pcu-direct*::
Indicate that an external PCU (e.g. OsmoPCU) will directly
- open the DSP messge queues to the PHY / PH-SAP, and only MPH
+ open the DSP message queues to the PHY / PH-SAP, and only MPH
primitives are passed via OsmoBTS.
@@ -225,7 +225,7 @@ human-readable format to current VTY session.
===== `osmotrx ip HOST`
-Set the IP addess of the OsmoTRX transceiver to which we should connect
+Set the IP address of the OsmoTRX transceiver to which we should connect
to.
===== `osmotrx base-port (local|remote) <0-65535>`
@@ -293,7 +293,7 @@ OCTPKT session, which is mapped to an OsmoBTS PHY link. Depending on
the OCTSDR-2G software version, you may create multiple software TRX by
creating multiple OsmoBTS PHY instances inside that PHY link.
-Multiple DSPs may exsist in one circuit board, then each of the DSPs is
+Multiple DSPs may exist in one circuit board, then each of the DSPs is
interfaced by one OsmoBTS PHY link, and each of them may have one or
more OsmoBTS PHY instances creating a Multi-TRX configuration.
diff --git a/OsmoBTS/chapters/interfaces.adoc b/OsmoBTS/chapters/interfaces.adoc
index f5bf1b2..a95f524 100644
--- a/OsmoBTS/chapters/interfaces.adoc
+++ b/OsmoBTS/chapters/interfaces.adoc
@@ -51,7 +51,7 @@ limited and largely depends on the bts_model used.
==== trx.N.thermal-attenuation
-The idea of this paramter is to attenuate the system output power as part of
+The idea of this parameter is to attenuate the system output power as part of
thermal management. In some cases the PA might be passing a critical level,
so an external control process can use this attribute to reduce the system
output power.
diff --git a/OsmoBTS/osmobts-abis.adoc b/OsmoBTS/osmobts-abis.adoc
index 6b4f0da..930cbfb 100644
--- a/OsmoBTS/osmobts-abis.adoc
+++ b/OsmoBTS/osmobts-abis.adoc
@@ -11,7 +11,7 @@ these are not or not fully implemented, as well as OsmoBTS-specific extensions
to the A-bis interface not specified by 3GPP.
Extensions to the A-bis interface specific to OsmoBTS are detailed in this
-document. For details on the messages and IEs that comply with abovementioned
+document. For details on the messages and IEs that comply with above mentioned
3GPP specifications, please refer to those documents.
.3GPP document versions referred to by this document
diff --git a/OsmoNITB/chapters/mncc.adoc b/OsmoNITB/chapters/mncc.adoc
index 2b75923..504ce09 100644
--- a/OsmoNITB/chapters/mncc.adoc
+++ b/OsmoNITB/chapters/mncc.adoc
@@ -181,7 +181,7 @@ NITB and an external MNCC handler.
Direction: both
-Transfer the payload of a GSM Enanced Full-Rate (EFR) voice frame
+Transfer the payload of a GSM Enhanced Full-Rate (EFR) voice frame
between the NITB and an external MNCC handler.
==== GSM_TCHH_FRAME
diff --git a/OsmoNITB/chapters/net.adoc b/OsmoNITB/chapters/net.adoc
index ecd0889..455e1a6 100644
--- a/OsmoNITB/chapters/net.adoc
+++ b/OsmoNITB/chapters/net.adoc
@@ -62,7 +62,7 @@ OpenBSC(config-net)# mobile network code 89
The __MM INFO__ procedure can be used after a successful __LOCATION
UPDATE__ in order to transmit the human-readable network name as well as
-local time zone information to the MS. gq
+local time zone information to the MS.
By default, MM INFO is not active. You can activate it, and set its
configuration using the VTY. An example is provided below.
diff --git a/OsmoNITB/chapters/running.adoc b/OsmoNITB/chapters/running.adoc
index 47b5eb7..423ecf7 100644
--- a/OsmoNITB/chapters/running.adoc
+++ b/OsmoNITB/chapters/running.adoc
@@ -29,7 +29,7 @@ arguments:
for more information.
*-T, --timestamp*::
Enable time-stamping of log messages to stderr. This has mostly
- been deprecated by VTY based logging configu- ration, see
+ been deprecated by VTY based logging configuration, see
<<logging>> for more information.
*-e, --log-level 'LOGLEVEL'*::
Set the global log level for logging to stderr. This has mostly
@@ -42,7 +42,7 @@ arguments:
Authorize every subscriber to the network. This corresponds to
the `auth-policy open` VTY configuration option.
+
- WARNING:: This is dangerous as you may disrupt sevices to
+ WARNING:: This is dangerous as you may disrupt services to
subscribers that are not part of your network! Don't use unless
you absolutely know what you're doing!
*-P, --rtp-proxy*::
diff --git a/OsmoNITB/chapters/smpp.adoc b/OsmoNITB/chapters/smpp.adoc
index 1550abd..2557580 100644
--- a/OsmoNITB/chapters/smpp.adoc
+++ b/OsmoNITB/chapters/smpp.adoc
@@ -37,7 +37,7 @@ ESMEs are permitted to access the SMSC (`closed`), or whether any
ESME should be accepted (`accept-all`).
Use the `smpp-first` command to define if SMPP routes have higher
-precendence than MSISDNs contained in the HLR (`smpp-first`), or if
+precedence than MSISDNs contained in the HLR (`smpp-first`), or if
only MSISDNs found not in the HLR should be considered for routing to
SMPP (`no smpp-first`).
diff --git a/OsmoPCU/chapters/configuration.adoc b/OsmoPCU/chapters/configuration.adoc
index 1a86f32..bcf3ad7 100644
--- a/OsmoPCU/chapters/configuration.adoc
+++ b/OsmoPCU/chapters/configuration.adoc
@@ -59,7 +59,7 @@ reached, a higher coding scheme is chosen.
You can use the `cs link-quality-ranges cs1 <0-35> cs2 <0-35> <0-35> cs3
<0-35> <0-35> cs4 <0-35>` command at the `pcu` VTY config node to tune
-the link quality ranges for the respecive coding schemes.
+the link quality ranges for the respective coding schemes.
==== Data Size based CS downgrade Threshold
@@ -114,7 +114,7 @@ filter).
==== Normal BSSGP Flow Control Tuning parameters
You can use the following commands at the `pcu` VTY config node to tune
-the the BSSGP flow control parameters:
+the BSSGP flow control parameters:
`flow-control-interval <1-10>`::
configure the interval (in seconds) between subsequent flow
@@ -185,7 +185,7 @@ parameters.
You can set those parameters at the `pcu` VTY config node as follows:
`alpha <0-10>`::
- Alpha parameter for MS power contrl in units of 0.1.
+ Alpha parameter for MS power control in units of 0.1.
Make sure to set the alpha value at System Information 13 (in
the BSC), too!
`gamma <0-62>`::
diff --git a/OsmoPCU/chapters/overview.adoc b/OsmoPCU/chapters/overview.adoc
index e13a7b8..0031474 100644
--- a/OsmoPCU/chapters/overview.adoc
+++ b/OsmoPCU/chapters/overview.adoc
@@ -6,7 +6,7 @@ OsmoPCU is the Osmocom implementation of the GPRS PCU (Packet Control
Unit) element inside the GPRS network.
The OsmoPCU is co-located within the BTS and connects to OsmoBTS via its
-PCU socket inteface.
+PCU socket interface.
On the other side, OsmoPCU is connected via the Gb interface to the
SGSN.
diff --git a/OsmoPCU/osmopcu-gb.adoc b/OsmoPCU/osmopcu-gb.adoc
index 7598900..fc2ca8f 100644
--- a/OsmoPCU/osmopcu-gb.adoc
+++ b/OsmoPCU/osmopcu-gb.adoc
@@ -72,7 +72,7 @@ NSVCI:: NS Virtual Connection Identifier
BVCI:: BSSGP Virtual Connection Identifier
For an explanation of those identifiers and their use in the NS and
-BSSGP protocols, please see the reelvant 3GPP specifications for NS (TS 08.16)
+BSSGP protocols, please see the relevant 3GPP specifications for NS (TS 08.16)
and BSSGP (TS 08.18).
In most cases, all above identities belong to different namespaces and
diff --git a/OsmoSGSN/chapters/configuration.adoc b/OsmoSGSN/chapters/configuration.adoc
index 0d010c3..8b259ed 100644
--- a/OsmoSGSN/chapters/configuration.adoc
+++ b/OsmoSGSN/chapters/configuration.adoc
@@ -125,7 +125,7 @@ The CDR file is a simple CSV file including a header line naming the
individual fields of each CSV line.
[[sgsn-cdr]]
-.Descripton of CSV fields in OsmoSGSN CDR file
+.Description of CSV fields in OsmoSGSN CDR file
[options="header",cols="15%,85%"]
|===
|Field Name|Description
diff --git a/OsmoSGSN/chapters/gsup.adoc b/OsmoSGSN/chapters/gsup.adoc
index 9efc8c0..838af7d 100644
--- a/OsmoSGSN/chapters/gsup.adoc
+++ b/OsmoSGSN/chapters/gsup.adoc
@@ -29,14 +29,14 @@ By default, the following identifiers should be used:
* IPA OSMO protocol extension: 0x05
For more information about the IPA multiplex, please see the 'OsmoBTS
-Abis/IP Specifiation'.
+Abis/IP Specification'.
=== Procedures
==== Authentication management
The SGSN sends a SEND_AUTHENTICATION_INFO_REQ message containing the MS's IMSI
-to the peer. On errors, especially if authentication info is not availabe for
+to the peer. On errors, especially if authentication info is not available for
that IMSI, the peer returns a SEND_AUTHENTICATION_INFO_ERR message. Otherwise
the peer returns a SEND_AUTHENTICATION_INFO_RES message. If this message
contains at least one authentication tuple, the SGSN replaces all tuples that
diff --git a/common/chapters/gb.adoc b/common/chapters/gb.adoc
index 793e23f..d01fa9b 100644
--- a/common/chapters/gb.adoc
+++ b/common/chapters/gb.adoc
@@ -58,7 +58,7 @@ The NS protocol features a number of configurable timers.
=== Examining Gb interface status
-There are several commans that can help to inspect and analyze the
+There are several commands that can help to inspect and analyze the
currently running system status with respect to the Gb interfaces.
.Example: Inspecting NS state
diff --git a/common/chapters/glossary.adoc b/common/chapters/glossary.adoc
index 4d68666..c39d439 100644
--- a/common/chapters/glossary.adoc
+++ b/common/chapters/glossary.adoc
@@ -8,7 +8,7 @@
3GPP::
3rd Generation Partnership Project
4FF::
- 4th Generaion Form Factor; the so-called nanoSIM form factor
+ 4th Generation Form Factor; the so-called nanoSIM form factor
A Interface::
Interface between BTS and BSC, traditionally over E1 (_3GPP TS 48.008_
<<3gpp-ts-48-008>>)
@@ -103,7 +103,7 @@ GGSN::
GMSK::
Gaussian Minimum Shift Keying; modulation used for GSM and GPRS
GPL::
- GNU General Public License, a copyleft-style Freee Software License
+ GNU General Public License, a copyleft-style Free Software License
Gp::
Gp interface between SGSN and GGSN; uses GTP protocol
GPS::
@@ -159,7 +159,7 @@ MNO::
MS::
Mobile Station; a mobile phone / GSM Modem
MSC::
- Mobile Switching Center; network element in the circuit-switcehd
+ Mobile Switching Center; network element in the circuit-switched
core network
MSISDN::
Mobile Subscriber ISDN Number; telephone number of the subscriber
@@ -168,7 +168,7 @@ MVNO::
NCC::
Network Color Code; assigned by national regulator
NITB::
- Network In The Box; combines functionality traditionally proivided
+ Network In The Box; combines functionality traditionally provided
by BSC, MSC, VLR, HLR, SMSC functions; see OsmoNITB
NSEI::
NS Entity Identifier
@@ -236,7 +236,7 @@ RFM::
Roaming::
Procedure in which a subscriber of one network is using the radio
network of another network, often in different countries; in some
- countris national roaming exists
+ countries national roaming exists
Routing Area::
Routing Area; GPRS specific sub-division of Location Area
RR::
diff --git a/common/chapters/preface.adoc b/common/chapters/preface.adoc
index d986cbe..13afec1 100644
--- a/common/chapters/preface.adoc
+++ b/common/chapters/preface.adoc
@@ -71,7 +71,7 @@ following key individuals and organizations, in no particular order:
annual Osmocom Developer Conference and releasing this manual.
* Jan Luebbe, Stefan Schmidt, Daniel Willmann, Pablo Neira, Nico Golde,
Kevin Redon, Ingo Albrecht, Alexander Huemer, Alexander Chemeris, Max
- Suraev, Tobias Engel, Jacob Erlbeck, Ivan Kluchnikov, Alexander Huemer
+ Suraev, Tobias Engel, Jacob Erlbeck, Ivan Kluchnikov
May the source be with you!
@@ -125,7 +125,7 @@ contributions can be many-fold, for example
by donating developer resources or by (partially) funding those people
in the community who do.
-We're looking forward to receicing your contributions.
+We're looking forward to receiving your contributions.
=== Osmocom and sysmocom
@@ -194,17 +194,17 @@ use case is compliant with the software licenses.
==== Trademarks
All trademarks, service marks, trade names, trade dress, product names
-and logos appearing in this manual are the property of their respecitve
+and logos appearing in this manual are the property of their respective
owners. All rights not expressly granted herein are reserved.
-For your convenience we have listed below some of the registrered
+For your convenience we have listed below some of the registered
trademarks referenced herein. This is not a definitive or complete list
of the trademarks used.
'Osmocom(R)' and 'OpenBSC(R)' are registered trademarks of Holger
Freyther and Harald Welte.
-'sysmocom(R)' and 'sysmoBTS(R)' is registered trasdemarks of
+'sysmocom(R)' and 'sysmoBTS(R)' are registered trademarks of
'sysmocom - systems for mobile communications GmbH'.
'ip.access(R)' and 'nanoBTS(R)' are registered trademarks of
diff --git a/common/chapters/vty.adoc b/common/chapters/vty.adoc
index 9103319..931cd1f 100644
--- a/common/chapters/vty.adoc
+++ b/common/chapters/vty.adoc
@@ -134,12 +134,12 @@ OpenBSC> <1>
terminal Set terminal line parameters
who Display who is on vty
logging Configure log message to this terminal
- sms SMS related comamnds
+ sms SMS related commands
subscriber Operations on a Subscriber
----
<1> press `?` here at the prompt, the character will not be printed
-If you have already entered a partial comamnd, `?` will help you to
+If you have already entered a partial command, `?` will help you to
review possible options of how to continue your command. Let's say you
remember that `show` is used to investigate the system status. But you
don't know exactly what the object was called that you'd like to show:
@@ -157,7 +157,7 @@ OpenBSC> show <1>
trx Display information about a TRX
timeslot Display information about a TS
lchan Display information about a logical channel
- paging Display information about paging reuqests of a BTS
+ paging Display information about paging requests of a BTS
paging-group Display the paging group
logging Show current logging configuration
alarms Show current logging configuration
@@ -172,7 +172,7 @@ OpenBSC> show <1>
----
<1> press `?` after the `show` command, the character will not be printed
-Now you decide you want to have a look at the the `network` object, so
+Now you decide you want to have a look at the `network` object, so
you type network and press `?` again:
.Example: Typing `?` after `show network`
--
1.9.1
