DigitalOcean changed its API changelog

===================================================================
--- before
+++ after
@@ -221,9 +221,9 @@
 SEPTEMBER 2022
 
 28 SEPTEMBER
 
- * Released v1.82.0 of doctl, the official DigitalOcean CLI. This release upgrades godo to v1.86.0 and adds support for building App Platform apps locally.
+ * Released v1.82.0 of doctl, the official DigitalOcean CLI. This release upgrades Godo to v1.86.0 and adds support for building App Platform apps locally.
    
    
 
 20 SEPTEMBER
@@ -303,9 +303,9 @@
 MAY 2022
 
 23 MAY
 
- * Released v1.76.0 of doctl, the official DigitalOcean CLI. This release adds support for our new serverless Functions product and updates godo to support new App Platform features.
+ * Released v1.76.0 of doctl, the official DigitalOcean CLI. This release adds support for our new serverless Functions product and updates Godo to support new App Platform features.
    
    
 
 10 MAY
@@ -323,9 +323,9 @@
 MARCH 2022
 
 31 MARCH
 
- * Released v1.73.0 of doctl, the official DigitalOcean CLI. This release updates godo to support new App Platform features.
+ * Released v1.73.0 of doctl, the official DigitalOcean CLI. This release updates Godo to support new App Platform features.
    
    
 
 29 MARCH
@@ -423,9 +423,9 @@
 NOVEMBER 2021
 
 10 NOVEMBER
 
- * Released v1.67.0 of doctl, the official DigitalOcean CLI. This release updates godo to support new App Platform features.
+ * Released v1.67.0 of doctl, the official DigitalOcean CLI. This release updates Godo to support new App Platform features.
    
    
 
 8 NOVEMBER
@@ -552,9 +552,9 @@
  * We have updated the Floating IP API responses to better align with our newer API models. The droplet and region fields now use the same response models used in the /v2/droplets and /v2/regions endpoints. Specifically:
    
    * The private_networking feature is now displayed under the features field under droplet instead of the features field under region.
    * The vpc_uuid field now populates with the correct values.
-   * The Droplet’s type displays base when the Droplet uses a base image (i.e. Ubuntu, CentOS).
+   * The Droplet’s type displays base when the Droplet uses a base image (for example, Ubuntu, CentOS).
    * The Droplet’s networks field now includes private and floating IP addresses, if applicable.
    
    
 
@@ -719,9 +719,9 @@
 2 NOVEMBER
 
  * You can now integrate your DOCR registry with a Kubernetes cluster. When a registry is integrated with a Kubernetes cluster, we create docker registry type secrets in all the namespaces in the cluster. These secrets can be used with the workloads or added to the default service account in the namespace.
    
-   Additionally, we’ve added DOCR integration support for our official clients, godo and doctl. Only versions of doctl 1.49.0 and godo 1.48.0 and above support docr integration for clusters.
+   Additionally, we’ve added DOCR integration support for our official clients, Godo and doctl. Only versions of doctl 1.49.0 and Godo 1.48.0 and above support docr integration for clusters.
    
    
 
 OCTOBER 2020
@@ -777,9 +777,9 @@
    
 
  * You can now apply taints to Kubernetes node pools. When you configure taints for a node pool, the taint automatically applies to all current nodes in the pool and any node you add to the pool thereafter. For more information about taints and tolerations, see Kubernetes’ documentation.
    
-   Additionally, we’ve added node taint support for our official clients, godo and doctl. Only versions of doctl 1.47.0 and godo 1.45.0 and above support persistent node pool taints.
+   Additionally, we’ve added node taint support for our official clients, Godo and doctl. Only versions of doctl 1.47.0 and Godo 1.45.0 and above support persistent node pool taints.
    
    You can define taints during a pool’s creation by submitting a POST request to the /v2/kubernetes/clusters/<cluster-id>/node_pools and the /v2/kubernetes/clusters endpoints, or you can update existing pools by submitting a PUT request to the /v2/kubernetes/clusters/<cluster-id>/node_pools/<node-pool-id> endpoint. For example, this request body defines two taints for a node pool.
    
    {
@@ -1099,9 +1099,9 @@
 DECEMBER 2019
 
 2 DECEMBER
 
- * The DigitalOcean API currently offers the ability to retrieve a report of all Droplets co-located on the same physical hardware by sending a GET request to the /v2/reports/droplet_neighbors endpoint. This endpoint has been deprecated and will begin responding with an HTTP status of 410 (Gone) on December 17th, 2019.
+ * The DigitalOcean API currently offers the ability to retrieve a report of all Droplets co-located on the same physical hardware by sending a GET request to the /v2/reports/droplet_neighbors endpoint. This endpoint has been deprecated and will begin responding with an HTTP status of 410 (Gone) on 17 December 2019.
    
    Today, in its place, a new endpoint is now available: /v2/reports/droplet_neighbors_ids. Rather than listing the full Droplet object, responses from this endpoint only contain sets of Droplet IDs co-located on the same physical hardware. For example:
    
    {
@@ -1192,9 +1192,9 @@
 JUNE 2019
 
 25 JUNE
 
- * The ttl of a domain record now has a minimum value of 30 seconds, and if not set, the default value has changed from 1,800 to the ttl of the SOA record.
+ * The TTL of a domain record now has a minimum value of 30 seconds, and if not set, the default value has changed from 1,800 to the TTL of the SOA record.
    
    
 
 MAY 2019
@@ -1202,9 +1202,9 @@
 30 MAY
 
  * DigitalOcean Managed Databases now provide support for private networking. All new database clusters will be provisioned with private networking enabled. Existing clusters will require an update to connect over the private network. This can be triggered in the control panel.
    
-   Databases, read-only replicas, and connection pools will now contain a new private_connection object holding the information needed to access the resource via the private network. Its attributes are identical to the existing connection object, but the values for private_connection.uri and private_connection.host will contain FQDNs only accessible from resources (e.g. Droplets or Kubernetes clusters) within your account and in the same region.
+   Databases, read-only replicas, and connection pools will now contain a new private_connection object holding the information needed to access the resource via the private network. Its attributes are identical to the existing connection object, but the values for private_connection.uri and private_connection.host will contain FQDNs only accessible from resources (for example, Droplets or Kubernetes clusters) within your account and in the same region.
    
    For more information, see the full managed databases API documentation.
    
    
@@ -1216,9 +1216,9 @@
    
 
  * Today, we are promoting the Kubernetes API to General Availability. As part of this release, we have also extended the API with additional functionality:
    
-   * When creating or updating a cluster, you may now configure a maintenance window policy specifying the day of the week and time of day that updates should take place for the cluster. Additionally, setting a cluster’s auto_upgrade attribute to true will specify that the cluster can be automatically upgraded to new Kubernetes patch releases (e.g. 1.13.1 to 1.13.2) during its maintenance window.
+   * When creating or updating a cluster, you may now configure a maintenance window policy specifying the day of the week and time of day that updates should take place for the cluster. Additionally, setting a cluster’s auto_upgrade attribute to true will specify that the cluster can be automatically upgraded to new Kubernetes patch releases (for example, 1.13.1 to 1.13.2) during its maintenance window.
    
    * An upgrade endpoint is now available to imminently trigger an upgrade to a newer patch release of Kubernetes at your own convenience. You may list available upgrades for your cluster using the upgrades endpoint.
    
    * In order to give users finer control over individual nodes, the recycle endpoint has been deprecated. Instead, we now offer the ability to delete or replace specific nodes in a node pool. By default, workloads will be drained from the node before deletion. Appending the skip_drain=1 query parameter to the request will cause the node to be imminently deleted. Appending the replace=1 query parameter to the request will cause the node to be replaced by a new one after it has been deleted.
@@ -1533,9 +1533,9 @@
    * Create, list, retrieve, update, and delete Projects
    * Assign existing resources to a Project
    * List resources in a Project
    
-   Additionally, we’ve added beta support for Projects to our official clients (Droplet Kit, godo, and doctl).
+   Additionally, we’ve added beta support for Projects to our official clients (Droplet Kit, Godo, and doctl).
    
    You can create a new project by sending a POST request to the /v2/projects endpoint including a body like:
    
    {
@@ -1559,9 +1559,9 @@
    
    
    Resources are identified by uniform resource names or URNs, a string consisting of the type of resource and its unique identifier. A valid URN has the following format: do:resource_type:resource_id. For the full details, see the API reference documentation for both Projects and Project Resources.
    
-   Note that as this is a beta release, we may make additional changes based on your feedback. So let us know how you’re using projects, and follow along with the API changelog for updates.
+   As this is a beta release, we may make additional changes based on your feedback. So let us know how you’re using projects, and follow along with the API changelog for updates.
    
    
 
 SEPTEMBER 2018
@@ -1616,9 +1616,9 @@
    
 
 5 SEPTEMBER
 
- * When listing or getting tags by sending a GET request to /v2/tags or /v2/tags/$TAG_NAME, the response payload currently includes a last_tagged value inside the tag’s resources.droplets containing a full representation of the resource. This payload is considerably nested and adds additional overhead to the request. In order to improve performance as well as lay the groundwork for bring tagging support to additional resources, this attribute is being deprecated. Beginning March 1st, 2019 last_tagged will no longer be populated in favor of the new last_tagged_uri attribute introduced today.
+ * When listing or getting tags by sending a GET request to /v2/tags or /v2/tags/$TAG_NAME, the response payload currently includes a last_tagged value inside the tag’s resources.droplets containing a full representation of the resource. This payload is considerably nested and adds additional overhead to the request. In order to improve performance as well as lay the groundwork for bring tagging support to additional resources, this attribute is being deprecated. Beginning 1 March 2019 last_tagged will no longer be populated in favor of the new last_tagged_uri attribute introduced today.
    
    For all resources (and each resource type supported), the last_tagged_uri attribute contains a string indicating the URI which can be used to retrieve details about that specific resource. If you need information about the last tagged resource specifically, issuing another call to that URI will provide you with all the data for that resource.
    
    Additionally, a count attribute describing how many resources overall have been tagged with the tag in question has been added. Each individual resource type will continue providing a count attribute.
@@ -1657,9 +1657,9 @@
      -H "Content-Type: application/json" \
      -H "Authorization: Bearer $DIGITALOCEAN_TOKEN" \
      https://api.digitalocean.com/v2/volumes
    
-   Additionally, Ubuntu, Debian, Fedora, Fedora Atomic, and CentOS Droplets created on or after April 26, 2018 will now automatically mount volumes with pre-formatted filesystems when attached. Attaching pre-formatted volumes to other Droplets is not recommended. When the filesystem_type attribute is not provided, volumes will continue to be presented as raw block devices and require additional configuration.
+   Additionally, Ubuntu, Debian, Fedora, Fedora Atomic, and CentOS Droplets created on or after 26 April 2018 will now automatically mount volumes with pre-formatted filesystems when attached. Attaching pre-formatted volumes to other Droplets is not recommended. When the filesystem_type attribute is not provided, volumes will continue to be presented as raw block devices and require additional configuration.
    
    When retrieving an existing volume, filesystem_type and filesystem_label will reflect the current filesystem and label used on the volume even if these were applied manually.
    
    For more information, see the full API documentation for Volumes.
@@ -1699,9 +1699,9 @@
 16 JANUARY
 
  * Today, we announced wide-ranging changes to our Droplet plans, bringing improved resources across the board. These new plans are now available via the API and can be referenced using their respective size slugs.
    
-   Size slugs are human-readable strings used to specify the type of Droplet in certain API requests. In the past, size slugs were typically based on the amount of RAM provided with the plan (e.g. 1gb). Moving forward, we are standardizing on a format comprised of the identifier for the Droplet’s class, the vCPU count, and the amount of RAM in order to provide more flexibility in the plans we are able to offer you. For example, our new $5 per month Standard Droplet comes with 1 vCPU and 1 GB of RAM. So its size slug is. s-1vcpu-1gb.
+   Size slugs are human-readable strings used to specify the type of Droplet in certain API requests. In the past, size slugs were typically based on the amount of RAM provided with the plan (for example, 1gb). Moving forward, we are standardizing on a format comprised of the identifier for the Droplet’s class, the vCPU count, and the amount of RAM in order to provide more flexibility in the plans we are able to offer you. For example, our new $5 per month Standard Droplet comes with 1 vCPU and 1 GB of RAM. Its size slug is s-1vcpu-1gb.
    
    Applications and scripts with hard-coded size slugs must be updated to take advantage of these new plans. In order to provide a transition period, 1st Generation Droplet plans will continue to be available via the API using the legacy size slugs. We will provide additional notice before their removal.
    
    The table below shows the new 2nd Generation Standard Droplet plans along with their corresponding size slug. For always up-to-date information on available plans and pricing, see our pricing page.
@@ -1741,9 +1741,9 @@
 MARCH 2017
 
 28 MARCH
 
- * Our API currently offers the ability to “rename” a tag by sending a PUT request to /v2/tags/$TAG_NAME. Due to low usage and operational complexities involved with its maintenance, we are deprecating this functionality. Beginning April 26th, 2017 all requests to this endpoint will respond with an HTTP status of 410 (Gone). A tag’s name also serves as its unique identifier. We’ve found that the ability to change a tag’s name introduces unneeded complexity. If you need guidance on this transition, reach out to the team by opening a support ticket.
+ * Our API currently offers the ability to “rename” a tag by sending a PUT request to /v2/tags/$TAG_NAME. Due to low usage and operational complexities involved with its maintenance, we are deprecating this functionality. Beginning 26 April 2017 all requests to this endpoint will respond with an HTTP status of 410 (Gone). A tag’s name also serves as its unique identifier. We’ve found that the ability to change a tag’s name introduces unneeded complexity. If you need guidance on this transition, reach out to the team by opening a support ticket.
    
    
 
 NOVEMBER 2016
@@ -1773,17 +1773,17 @@
 MARCH 2016
 
 22 MARCH
 
- * API v2 now supports tagging and managing tagged droplets.
+ * API v2 now supports tagging and managing tagged Droplets.
    
    
 
 DECEMBER 2015
 
 14 DECEMBER
 
- * API v2 now supports creating multiple droplets simultaneously.
+ * API v2 now supports creating multiple Droplets simultaneously.
    
    
 
 NOVEMBER 2015
@@ -1825,9 +1825,9 @@
 1 MAY
 
  * Since releasing version 2 of our API nearly a year ago and officially bringing it out of beta last month, we’ve seen a tremendous uptake of usage by our community. As the ecosystem of tools and libraries continues to grow, we’ve decided that it is time to sunset version 1 of the API.
    
-   Don’t worry! We’re not going to pull the rug out from under you. In order to give everyone time to port their tools, version 1 will not be turned off until Monday, November 9, 2015.
+   To give everyone time to port their tools, version 1 will not be turned off until Monday, 9 November 2015.
    
    With its (more) RESTful interface and features like OAuth support, v2 is both powerful and easy to use. Our developer documentation should give you all the information you need to begin the transition. If you have questions, you can always ask on our Community site or on Twitter.
    
    
@@ -1863,9 +1863,9 @@
 FEBRUARY 2015
 
 20 FEBRUARY
 
- * All action objects, i.e. those returned by the /v2/actions, /v2/droplets/$ID/actions and /v2/images/$ID/actions endpoint now return a region_slug attribute, in addition to a region attribute. At 00:01 March 20, 2015 UTC, API v2 will start returning an embedded region object at the region attribute, not a slug.
+ * All action objects, that is, those returned by the /v2/actions, /v2/droplets/$ID/actions and /v2/images/$ID/actions endpoint now return a region_slug attribute, in addition to a region attribute. At 00:01 UTC on 20 March 2015, API v2 will start returning an embedded region object at the region attribute, not a slug.
    
    For example, the API request:
    
    curl -X GET -H 'Content-Type: application/json' \
@@ -1924,9 +1924,9 @@
    
 
 10 FEBRUARY
 
- * Two new endpoints in API v2 report if droplets are running on the same physical hardware. They exist for an individual droplet or for an entire account.
+ * Two new endpoints in API v2 report if Droplets are running on the same physical hardware. They exist for an individual Droplet or for an entire account.
    
    
 
 8 FEBRUARY
@@ -1954,9 +1954,9 @@
 NOVEMBER 2014
 
 6 NOVEMBER
 
- * The API v2 now supports retrieving images by type, to retrieve an image by type, simply append:
+ * The API v2 now supports retrieving images by type. To retrieve an image by type, append:
    
    GET /v2/images?type={distribution,application}
    
    Change type to what you would like to retrieve and voilà!
@@ -1970,11 +1970,11 @@
 OCTOBER 2014
 
 27 OCTOBER
 
- * The JSON object for a droplet no longer contains a nested Size object, but rather a slug called size_slug that references a Size object. See the droplet docs for the updated structure.
+ * The JSON object for a Droplet no longer contains a nested Size object, but rather a slug called size_slug that references a Size object. See the Droplet docs for the updated structure.
    
-   The Image JSON object now includes a min_disk_size attribute that contains the slug of the minimum size droplet required for that image. For example a snapshot of a 1 Gig droplet will have “1gb” as it’s min_disk_size.
+   The Image JSON object now includes a min_disk_size attribute that contains the slug of the minimum size Droplet required for that image. For example a snapshot of a 1 Gig Droplet will have “1gb” as its min_disk_size.
    
    
 
 AUGUST 2014
@@ -2006,9 +2006,9 @@
  * API V2 now supports disabling backups on a Droplet.
    
    
 
- * API V2 now supports expanding a droplet’s disk size, along with other resources.
+ * API V2 now supports expanding a Droplet’s disk size, along with other resources.
    
    
 
  * Want to know which regions support IPv6 or Private Networking? It is now possible to check which features are enabled in each region.