From c14dedd7596a1672c7b6d90fee5e8066610b609c Mon Sep 17 00:00:00 2001 From: Yegor Yefremov Date: Sat, 18 Nov 2023 16:35:16 +0100 Subject: [PATCH] docs: fix typos --- docs/arch.rst | 2 +- docs/ndb_init.rst | 2 +- docs/parser.rst | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/arch.rst b/docs/arch.rst index d0ea452c0..387983a1f 100644 --- a/docs/arch.rst +++ b/docs/arch.rst @@ -74,7 +74,7 @@ match responses, and the pair `put()/get()` does it. cache thread ------------ -Sometimes it is preferrable to get incoming messages asap +Sometimes it is preferable to get incoming messages asap and parse them only when there is time for that. For that case the `NetlinkSocketBase` provides a possibility to start a dedicated cache thread, that will collect and queue incoming diff --git a/docs/ndb_init.rst b/docs/ndb_init.rst index 590ff4aca..6697100ab 100644 --- a/docs/ndb_init.rst +++ b/docs/ndb_init.rst @@ -81,7 +81,7 @@ sources 2020-03-24 18:01:48,537 DEBUG pyroute2.ndb.139900805197264.sources.test02: running -The RTNL sources documenation: :ref:`ndbsources` +The RTNL sources documentation: :ref:`ndbsources` db_provider, db_spec ~~~~~~~~~~~~~~~~~~~~ diff --git a/docs/parser.rst b/docs/parser.rst index 5bc9666ce..b070020ce 100644 --- a/docs/parser.rst +++ b/docs/parser.rst @@ -198,8 +198,8 @@ Mandatory message fields, expected by NetlinkSocketBase methods: Per-request parsers ------------------- -Sometimes it may be reasonable to handle a particular response with a -spcific parser, rather than a generic one. An example is +Sometimes, it may be reasonable to handle a particular response with a +specific parser rather than a generic one. An example is `IPRoute.get_default_routes()`, which could be slow on systems with huge amounts of routes.