ENGDOCS-2288

Author: sarahsanders-docker

content/manuals/docker-hub/download-rate-limit.md

@@ -64,9 +64,9 @@ The file contains the following comma separated values:
 | `access_token_name`  | Name of the access token that was used for authentication with Docker CLI. `generated` tokens are automatically generated by the Docker client when a user signs in.                                              | Personal access tokens are usually used to authenticate automated tools (Docker Desktop, CI/CD tools, etc.). This is useful for identifying which automated system issued the pull. |
 | `ips`                | The IP address that was used to pull the image. This field is aggregated, so more than one IP address may appear, representing all the IPs used to pull an image within the same date and hour.                            | This helps you understand the origin of the data transfer, which is useful for diagnosing and identifying patterns in automated or manual pulls.                                    |
 | `repository_privacy` | The privacy state of the image repository that was pulled. This can either be `public` or `private`.                                                                                                                       | This distinguishes between public and private repositories to identify which data transfer threshold the pull impacts.                                                              |
-| `tag`                | The tag for the image. The tag is only available if the pull request included a tag.                                                                                                                                       | This helps in identifying the image. Tags are often used to identify specific versions or variants of an image.                                                                     |
+| `tag`                | The tag for the image. The tag is only available if the pull included a tag.                                                                                                                                       | This helps in identifying the image. Tags are often used to identify specific versions or variants of an image.                                                                     |
 | `digest`             | The unique image digest for the image.                                                                                                                                                                                     | This helps in identifying the image.                                                                                                                                                |
-| `version_checks`     | The number of version checks accumulated for the date and hour of each image repository. Depending on the client, a pull request can do a version check to verify the existence of an image or tag without downloading it. | This helps identify the frequency of version checks, which you can use to analyze usage trends and potential unexpected behaviors.                                                  |
+| `version_checks`     | The number of version checks accumulated for the date and hour of each image repository. Depending on the client, a pull can do a version check to verify the existence of an image or tag without downloading it. | This helps identify the frequency of version checks, which you can use to analyze usage trends and potential unexpected behaviors.                                                  |
 | `pulls`              | The number of pulls accumulated for the date and hour of each image repository.                                                                                                                                            | This helps identify the frequency of repository pulls, which you can use to analyze usage trends and potential unexpected behaviors.                                                |
 
 ### Optimize and manage Docker Hub usage
@@ -134,17 +134,18 @@ charged at an on-demand rate. You can [scale your
 limit](../subscription/scale.md) or [upgrade](../subscription/change.md) to get
 a higher limit.
 
-## Pull request limit and rate limit
+## Pull limit and rate limit
 
-A pull request is defined as the following:
+A pull is defined as the following:
 
- - A Docker pull request includes both a version check and any download that
+ - A Docker pull includes both a version check and any download that
    occurs as a result of the pull. Depending on the client, a `docker pull` can
    verify the existence of an image or tag without downloading it by performing
    a version check.
- - A pull request for a normal image makes one pull for a [single
+ - Version checks do not count towards usage pricing.
+ - A pull for a normal image makes one pull for a [single
    manifest](https://github.com/opencontainers/image-spec/blob/main/manifest.md).
- - A pull request for a multi-arch image will count as one pull for each
+ - A pull for a multi-arch image will count as one pull for each
    different architecture.
  - Pulls are attributed to the user doing the pull, not to the owner of the
    image.
@@ -174,11 +175,11 @@ When pulling an image from an account linked to a verified domain, the attributi
 
 If the user is part of multiple organizations under the company, the pull is attributed to the user's personal namespace.
 
-### Pull request limit
+### Pull limit
 
 {{< include "hub-limits.md" >}}
 
-The pull request limit is calculated on a per month basis and only applies to
+The pull limit is calculated on a per month basis and only applies to
 Docker Pro, Docker Team, and Docker Business users. The limit automatically
 scales on-demand, but on-demand rates do apply. You can [scale your
 limit](../subscription/scale.md) or [upgrade](../subscription/change.md) to get
@@ -195,12 +196,12 @@ for each subscription tier, subject to fair use:
 | Personal (authenticated) | Not applicable       |
 | Unauthenticated users    | Not applicable       |
 
-### Pull request rate limit
+### Pull rate limit
 
-The pull request rate limit is calculated on a per hour basis. There is no
+The pull rate limit is calculated on a per hour basis. There is no
 pull rate limit for users or automated systems with a paid subscription.
 Unauthenticated and Docker Personal users using Docker Hub will experience rate
-limits on image pull requests.
+limits on image pulls.
 
 The following table describes the pull rate limit per hour
 for each subscription tier, subject to fair use:
@@ -218,11 +219,11 @@ for each subscription tier, subject to fair use:
 > Always sign in to Docker. Authenticated Docker Personal users receive
 > increased rate limits, while authenticated Docker Pro, Team, and Business
 > users are not rate limited. For more information, see [How do I authenticate
-> pull requests](#how-do-i-authenticate-pull-requests).
+> pulls](#how-do-i-authenticate-pull-requests).
 
-#### How do I know my pull requests are being limited?
+#### How do I know my pulls are being limited?
 
-When you issue a pull request and you are over the limit, Docker Hub returns a
+When you issue a pull and you are over the limit, Docker Hub returns a
 `429` response code with the following body when the manifest is requested:
 
 ```text
@@ -311,10 +312,10 @@ You can differentiate between these limits by looking at the error code. The
 "overall limit" returns a simple `429 Too Many Requests` response. The pull
 limit returns a longer error message that includes a link to this page.
 
-### How do I authenticate pull requests?
+### How do I authenticate pulls?
 
 The following section contains information on how to sign in to Docker Hub to
-authenticate pull requests.
+authenticate pulls.
 
 #### Docker Desktop