fix table

Signed-off-by: Craig <craig.osterhout@docker.com>

content/manuals/docker-hub/usage.md

@@ -33,7 +33,7 @@
 
 When utilizing the Docker Platform, users should be aware that excessive data
 transfer, pull rates, or data storage can lead to throttling, or additional
 charges. To ensure fair resource usage and maintain service quality, we reserve
 the right to impose restrictions or apply additional charges to accounts
 exhibiting excessive data and storage consumption.
 
@@ -243,13 +243,13 @@
 | `datehour`           | The date and hour (`yyyy/mm/dd/hh`) of the pull that resulted in the data transfer.                                                                                                                                | This helps in identifying peak usage times and patterns.                                                                                                                            |
 | `user_name`          | The Docker ID of the user that pulled the image                                                                                                                                                                    | This lets organization owners track data consumption per user and manage resources effectively.                                                                                     |
 | `repository`         | The name of the repository of the image that was pulled.                                                                                                                                                           | This lets you identify which repositories are most frequently accessed and consume most of the data transfer.                                                                       |
 | `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 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 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.
+| `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 usage
 
@@ -266,14 +266,14 @@
    - Inefficient pull behavior: Identify frequently accessed repositories to
      assess whether you can optimize caching practices or consolidate usage to
      reduce pulls.
    - Inefficient automated systems: Check which automated tools, such as CI/CD
      pipelines, may be causing higher pull rates, and configure them to avoid
      unnecessary image pulls.
 
 3. Optimize image pulls by:
 
    - Using caching: Implement local image caching via
      [mirroring](/docker-hub/mirror/) or within your CI/CD pipelines to reduce
      redundant pulls.
    - Automating manual workflows: Avoid unnecessary pulls by configuring automated
      systems to pull only when a new version of an image is available.