diff options
| author | Steve Martinelli <stevemar@ca.ibm.com> | 2015-03-07 14:24:37 -0500 |
|---|---|---|
| committer | Steve Martinelli <stevemar@ca.ibm.com> | 2015-03-07 19:28:21 +0000 |
| commit | ad8049741ee2e8621b052b5c342da408970c7601 (patch) | |
| tree | 42574ab91f30e9217ff99fa2a2697d3a023c22de | |
| parent | e935333aa4810c1a154d2a2136e4d1845d16f2a4 (diff) | |
| download | pycadf-ad8049741ee2e8621b052b5c342da408970c7601.tar.gz | |
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
| -rw-r--r-- | doc/source/specification/geolocations.rst | 11 |
1 files changed, 5 insertions, 6 deletions
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, |