[#3661] addressed review comments

diff --git a/changelog_unreleased/3661-arm-update-tuple-definition b/changelog_unreleased/3661-arm-update-tuple-definition
index e45121416c923c462176453ab6bcbff74ea12010..898c5926ce89e6879c161420d00b9d8e6ed10794 100644 (file)
--- a/changelog_unreleased/3661-arm-update-tuple-definition
+++ b/changelog_unreleased/3661-arm-update-tuple-definition
@@ -1,4 +1,4 @@
 [doc]          piotrek
-       Added more extensive definition of the tuple DHCP option type in
+       Added a more extensive definition of the tuple DHCP option type in
        the ARM documentation.
        (Gitlab #3661)

diff --git a/doc/sphinx/arm/dhcp4-srv.rst b/doc/sphinx/arm/dhcp4-srv.rst
index e7c27b7639c1f5ed3df64cb18d8168a77ff7206b..899860c6253d5a59fa1b461937b2e6be132dd602 100644 (file)
--- a/doc/sphinx/arm/dhcp4-srv.rst
+++ b/doc/sphinx/arm/dhcp4-srv.rst
@@ -2204,7 +2204,7 @@ what values are accepted for them.
    |                 | or 16-bit unsigned integer followed by                |
    |                 | a string of this length. Typically, for DHCPv4,       |
    |                 | the length is 8-bit, and for DHCPv6, it is 16-bit.    |
-   |                 | However, there might be exceptions to that rule.      |
+   |                 | However, there are exceptions to that rule.           |
    |                 | E.g. for the DHCPv4 SZTP Redirect Option,             |
    |                 | bootstrap-server-list is encoded as a list of         |
    |                 | tuples where the URI-length in each tuple is          |