laforge has uploaded this change for review.
chapters/*: Fix typos
Change-Id: I3c5cc64435c808f981d705d1d99c89fde2a6a74e
---
M common/chapters/gb-ns2.adoc
M common/chapters/glossary.adoc
M common/chapters/installation.adoc
M common/chapters/logging.adoc
M common/chapters/mgwpool.adoc
M common/chapters/oap.adoc
M common/chapters/preface.adoc
M common/chapters/qos-dscp-pcp.adoc
8 files changed, 23 insertions(+), 14 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-gsm-manuals refs/changes/06/32006/1
diff --git a/common/chapters/gb-ns2.adoc b/common/chapters/gb-ns2.adoc
index 925f515..e72fa50 100644
--- a/common/chapters/gb-ns2.adoc
+++ b/common/chapters/gb-ns2.adoc
@@ -249,7 +249,7 @@
static configuration
The static configuration requires to configure all endpoints on the BSS and SGSN.
-In constrast the dynamic configuration allows the SGSN to have only a reduced configuration.
+In contrast the dynamic configuration allows the SGSN to have only a reduced configuration.
===== Gb over IP "ip.access style" dynamic configuration
diff --git a/common/chapters/glossary.adoc b/common/chapters/glossary.adoc
index 7c706b9..bbddcc5 100644
--- a/common/chapters/glossary.adoc
+++ b/common/chapters/glossary.adoc
@@ -136,7 +136,7 @@
GSM tap; pseudo standard for encapsulating GSM protocol layers over
UDP/IP for analysis
GSUP::
- Generic ubscriber Update Protocol. Osmocom-specific alternative to TCAP/MAP
+ Generic Subscriber Update Protocol. Osmocom-specific alternative to TCAP/MAP
GT::
Global Title; an address in SCCP
GTP::
diff --git a/common/chapters/installation.adoc b/common/chapters/installation.adoc
index a3193fa..55b7e60 100644
--- a/common/chapters/installation.adoc
+++ b/common/chapters/installation.adoc
@@ -60,9 +60,9 @@
In general, the usual approach is to
-* start with `libosmocore` and all the required librarires and build
+* start with `libosmocore` and all the required libraries and build
them in order until you have the full chain of dependencies in place.
As a final step, build the actual application you want to use.
-* perform `autoreconf -fi`, `./confiugre` and `make install` for each of
+* perform `autoreconf -fi`, `./configure` and `make install` for each of
the projects. Check the `./configure --help` output to see which
optional compile-time features you might want to enable or disable.
diff --git a/common/chapters/logging.adoc b/common/chapters/logging.adoc
index b0a1f5e..a832ca4 100644
--- a/common/chapters/logging.adoc
+++ b/common/chapters/logging.adoc
@@ -32,7 +32,7 @@
different category, allowing fine-grained control over which log
messages you will or will not see. For example, in OsmoBSC, there are
categories for the protocol layers `rsl`, `rr`, `mm`,
-`cc` and many others. To get a a list of categories interactively
+`cc` and many others. To get a list of categories interactively
on the vty, type: `logging level ?`
[[log_levels]]
diff --git a/common/chapters/mgwpool.adoc b/common/chapters/mgwpool.adoc
index c8f2009..c4cf28a 100644
--- a/common/chapters/mgwpool.adoc
+++ b/common/chapters/mgwpool.adoc
@@ -66,7 +66,7 @@
The VTY implements a 'show mgw-pool' command that lists the currently configured
MGW pool members, their status and call utilization. The following snippet shows
an output example run on OsmoBSC, but it should be also available on other
-applications supporting the MGW pooling VTY featues:
+applications supporting the MGW pooling VTY features:
----
OsmoBSC> show mgw-pool
@@ -88,7 +88,7 @@
However it is still possible to assign any number from 0-255. The enumeration
also may contain gaps. The following snippet shows an output example run on
OsmoBSC, but it should be also available on other applications supporting the
-MGW pooling VTY featues:
+MGW pooling VTY features:
----
OsmoBSC> enable
@@ -163,7 +163,7 @@
happens locally to forward the UDP datagrams properly. Also (unless a reset
endpoint is configured like in the example config above) there will be no
immediate interaction with the MGW. However, the log should at least confirm
-the the connect worked and the MGCP client has been created successfully.
+the connect worked and the MGCP client has been created successfully.
----
Mon Aug 2 17:15:00 2021 DLMGCP mgcp_client.c:788 MGCP client: using endpoint domain '@mgw'
diff --git a/common/chapters/oap.adoc b/common/chapters/oap.adoc
index ad91f36..425ff75 100644
--- a/common/chapters/oap.adoc
+++ b/common/chapters/oap.adoc
@@ -81,7 +81,7 @@
authenticity and validity of the sequence number (included in AUTN), and, if
valid, reply with a CHALLENGE_RES message. This shall contain an XRES
authentication token generated by milenage from the same random bytes received
-from the server and the same shared secet. If the client decides to cancel the
+from the server and the same shared secret. If the client decides to cancel the
registration (e.g. invalid AUTN), it shall not reply to the CHALLENGE_REQ; a
CHALLENGE_ERR message may be sent, but is not mandatory. For example, the
client may directly start with a new REGISTER_REQ message.
diff --git a/common/chapters/preface.adoc b/common/chapters/preface.adoc
index b8f7e72..272f84a 100644
--- a/common/chapters/preface.adoc
+++ b/common/chapters/preface.adoc
@@ -117,13 +117,13 @@
is about sharing ideas and code, but also about sharing the effort of
software development and maintenance.
-If your organization is benefitting from using Osmocom software, please
+If your organization is benefiting from using Osmocom software, please
consider ways how you can contribute back to that community. Such
contributions can be many-fold, for example
* sharing your experience about using the software on the public mailing
lists, helping to establish best practises in using/operating it,
-* providing qualified bug reports, work-arounds
+* providing qualified bug reports, workarounds
* sharing any modifications to the software you may have made, whether
bug fixes or new features, even experimental ones
* providing review of patches
diff --git a/common/chapters/qos-dscp-pcp.adoc b/common/chapters/qos-dscp-pcp.adoc
index 3f97941..81a9e4e 100644
--- a/common/chapters/qos-dscp-pcp.adoc
+++ b/common/chapters/qos-dscp-pcp.adoc
@@ -77,7 +77,7 @@
header.
NOTE:: This means that PCP functionality requires the use of IEEE 802.q
-VLAN. You cannot use PCP without VLAN
+VLAN. You cannot use PCP without VLAN.
The Linux kernel assigns IEEE 802.1q PCP bits based on a _mapping_
between the _priority_ and the PCP value. Each VLAN network device
@@ -148,7 +148,7 @@
. configure the osmocom program to set the DSCP value
. use the default DSCP -> priority mapping, if possible
-. configure an egrees QoS map to map from priority to PCP
+. configure an egress QoS map to map from priority to PCP
If the desired combination of DSCP + PCP cannot be achieved that way,
due to the rather static default kernel mapping table, one needs to go
@@ -156,6 +156,6 @@
. configure the osmocom program to set the DSCP value
. use packet filter rules to set the priority based on DSCP
-. configure an egrees QoS map to map from priority to PCP
+. configure an egress QoS map to map from priority to PCP
include::{srcdir}/chapters/qos-example.adoc[]
To view, visit change 32006. To unsubscribe, or for help writing mail filters, visit settings.