diff --git a/doc/source/deployment_guide.rst b/doc/source/deployment_guide.rst
index 7458c4f2c1..c8aae9e555 100644
--- a/doc/source/deployment_guide.rst
+++ b/doc/source/deployment_guide.rst
@@ -101,8 +101,12 @@ into consideration can include physical location, power availability, and
 network connectivity. For example, in a small cluster you might decide to
 split the zones up by cabinet, with each cabinet having its own power and
 network connectivity. The zone concept is very abstract, so feel free to use
-it in whatever way best isolates your data from failure. Zones are referenced
-by number, beginning with 1.
+it in whatever way best isolates your data from failure. Each zone exists
+in a region.
+
+A region is also an abstract concept that may be used to distinguish between
+geographically separated areas as well as can be used within same datacenter.
+Regions and zones are referenced by a positive integer.
 
 You can now start building the ring with::
 
diff --git a/doc/source/overview_ring.rst b/doc/source/overview_ring.rst
index 321b5ac8bc..c6aa882381 100644
--- a/doc/source/overview_ring.rst
+++ b/doc/source/overview_ring.rst
@@ -80,7 +80,8 @@ the list of devices is a dictionary with the following keys:
 
 ======  =======  ==============================================================
 id      integer  The index into the list devices.
-zone    integer  The zone the devices resides in.
+zone    integer  The zone the device resides in.
+region  integer  The region the zone resides in.
 weight  float    The relative weight of the device in comparison to other
                  devices. This usually corresponds directly to the amount of
                  disk space the device has compared to other devices. For