Conflicting use of ports in "Creating keystone services and service endpoint" section of Essex "Install and Deploy" manual

In section "Creating keystone services and service endpoint" section of Essex "Install and Deploy" manual, at top of section re "endpoint-create" for "Keystone Identity Service". network ports used for for "publicurl", "internalurl", and "adminurl" differ from what is used later in section.

At top of section, doc indicates use of port 5000 for "publicurl" and "internalurl", and port 35357 for "adminurl" as here:

$ keystone --token 012345SECRET99TOKEN012345 \
 --endpoint http://192.168.206.130:35357/v2.0
 endpoint-create \
 --region RegionOne \
 --service_id=15c11a23667e427e91bc31335b45f4bd \
 --publicurl=http://192.168.206.130:5000/v2.0 \
 --internalurl=http://192.168.206.130:5000/v2.0 \
 --adminurl=http://192.168.206.130:35357/v2.0

In bottom of section, "For the Identity service you also create an endpoint.", doc indicates use of port 35357 for "publicurl" and "internalurl", and port 5000 for "adminurl" as here:

keystone --token 012345SECRET99TOKEN012345 --endpoint http://192.168.206.130:35357/v2.0 endpoint-create \
                       --region RegionOne \
                       --service_id=<id returned from endpoint creation> \
                       --publicurl http://192.168.206.130:35357/v2.0 \
                       --adminurl http://192.168.206.130:5000/v2.0 \
                       --internalurl http://192.168.206.130:35357/v2.0

So it's unclear to reader of this doc for which urls port 5000 should be used and for which urls port 35357 should be used, as the two examples contradict each other.

- Jim Collins