Reformatting timestamp in geography schema

Author: janedotx

policy/README.md

@@ -303,8 +303,8 @@ The internal mechanics of ordering are up to the Policy editing and hosting soft
 | `description`    | String    | O   | Detailed description of geography                                                                      |
 | `geography_id`   | UUID      | R   | Unique ID of geography                                                                 |
 | `geography_json`   | UUID      | R   | The GeoJSON that defines the geographical coordinates.
-| `effective_date`   | timestamp | O   | `start_date` for first published policy that uses this geo.  Server should set this when policies are published.  This may be used on the client to distinguish between “logical” geographies that have the same name. E.g. if a policy publishes a geography on 5/1/2020, and then another policy is published which references that same geography is published on 4/1/2020, the effective_date will be set to 4/1/2020.
-| `publish_date`   | timestamp | R   | Timestamp that the policy was published, i.e. made immutable                                             |
+| `effective_date`   | [timestamp][ts] | O   | `start_date` for first published policy that uses this geo.  Server should set this when policies are published.  This may be used on the client to distinguish between “logical” geographies that have the same name. E.g. if a policy publishes a geography on 5/1/2020, and then another policy is published which references that same geography is published on 4/1/2020, the effective_date will be set to 4/1/2020.
+| `publish_date`   | [timestamp][ts] | R   | Timestamp that the policy was published, i.e. made immutable                                             |
 | `prev_geographies`  | UUID[]    | O   | Unique IDs of prior geographies replaced by this one                                   |