summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorIlya Etingof <ietingof@redhat.com>2017-02-01 13:03:37 +0100
committerIlya Etingof <ietingof@redhat.com>2017-02-01 13:03:37 +0100
commit4231840d61bc9b7dd8a6012bd065f2411e0dd318 (patch)
tree11d62242d4fe589b55e4a4668aa37e9386db8c38
parent6d75ed7b21c05c959a4a56e1ff72b7e6f495512e (diff)
parent69635a3bdfeda38a723479e7a03890194e8ca345 (diff)
downloadpysnmp-git-4231840d61bc9b7dd8a6012bd065f2411e0dd318.tar.gz
Merge branch 'master' of github.com:etingof/pysnmp
-rw-r--r--docs/source/docs/snmp-design.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/source/docs/snmp-design.rst b/docs/source/docs/snmp-design.rst
index 522dc365..de349bf8 100644
--- a/docs/source/docs/snmp-design.rst
+++ b/docs/source/docs/snmp-design.rst
@@ -104,8 +104,8 @@ represented by Python objects that look like either a string or an
integer.
We can convert PyASN1 objects into Python types and back. PyASN1
-objects can participate in basic arethmetic operations (numbers)
-or in operations with strings (concatination, subscrption etc).
+objects can participate in basic arithmetic operations (numbers)
+or in operations with strings (concatenation, subscription etc).
All SNMP base types are immutable like their Python counterparts.
.. code-block:: python
@@ -198,7 +198,7 @@ Every managed device keeps a database of values for each of the
definitions written in the MIB. So, the available data is actually not
dependent on the database, but on the implementation. It is important
to realize that MIB files never contain data, they are functionally
-similar to database schemas rather than datastores.
+similar to database schemas rather than data stores.
To organize MIB modules and objects properly, all the manageable
features of all products (from each vendor) are arranged in this MIB