From 44c24f3c94402938aa62d2bfc00f6d28867521f8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Petr=20=C5=A0pa=C4=8Dek?= Date: Fri, 1 Jul 2022 13:26:36 +0200 Subject: [PATCH] Remove dotted_decimal from grammar glossary This definition was dererenced only once, from ip4_addr definition on the next line. These two are now collapsed into new ip4_addr definition. --- doc/arm/reference.rst | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/doc/arm/reference.rst b/doc/arm/reference.rst index ecb456f3c7..f1c391b653 100644 --- a/doc/arm/reference.rst +++ b/doc/arm/reference.rst @@ -287,11 +287,10 @@ file documentation: ``domain_name`` A quoted string which is used as a DNS name; for example: ``my.test.domain``. - ``dotted_decimal`` - One to four integers valued 0 through 255 and separated by dots (``.``), such as ``123.45.67`` or ``89.123.45.67``. - ``ip4_addr`` - An IPv4 address with exactly four elements in ``dotted_decimal`` notation, such as ``192.168.1.1``. + An IPv4 address with exactly four integer elements valued 0 through 255 + and separated by dots (``.``), such as ``192.168.1.1``. (A + "dotted-decimal" notation with all four elements present.) ``ip6_addr`` An IPv6 address, such as ``2001:db8::1234``. IPv6-scoped addresses that have ambiguity on their scope zones must be disambiguated by an appropriate zone ID with the percent character (``%``) as a delimiter. It is strongly recommended to use string zone names rather than numeric identifiers, to be robust against system configuration changes. However, since there is no standard mapping for such names and identifier values, only interface names as link identifiers are supported, assuming one-to-one mapping between interfaces and links. For example, a link-local address ``fe80::1`` on the link attached to the interface ``ne0`` can be specified as ``fe80::1%ne0``. Note that on most systems link-local addresses always have ambiguity and need to be disambiguated.