From ad8049741ee2e8621b052b5c342da408970c7601 Mon Sep 17 00:00:00 2001 From: Steve Martinelli Date: Sat, 7 Mar 2015 14:24:37 -0500 Subject: Fix formatting error for geolocation note The section was more of a `note` than an `example`, and renders more clearly when the rst `note` tag is used. Change-Id: I7b7c92301ce2bcfa60b44a0297eeb3848d89355e --- doc/source/specification/geolocations.rst | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) (limited to 'doc') diff --git a/doc/source/specification/geolocations.rst b/doc/source/specification/geolocations.rst index 6bfbdc1..1bd534a 100644 --- a/doc/source/specification/geolocations.rst +++ b/doc/source/specification/geolocations.rst @@ -57,13 +57,12 @@ Usage Requirements That is, all properties SHALL consistently represent the same geographic location and SHALL NOT provide conflicting value data. -:: +.. note:: - Example: 'latitude', 'longitude' and 'region' are all supplied as - properties describing the same geolocation, the 'latitude' and - 'longitude' properties' coordinate values should resolve to the - same geographic location as described by the 'region' - property's value. + `latitude`, `longitude` and `region` are all supplied as properties + describing the same geolocation, the `latitude` and `longitude` properties + coordinate values should resolve to the same geographic location as + described by the value of the `region` property. 4. ICANN's implementation plan states "Upper and lower case characters are considered to be syntactically and semantically identical"; therefore, -- cgit v1.2.1