convert to tables

Signed-off-by: Craig Osterhout <[email protected]>

Author: craig-osterhout

content/manuals/docker-hub/repos/manage/trusted-content/dvp-program.md

@@ -72,8 +72,9 @@ benefits from:
   across multiple availability zones, with load-balanced autoscaling, enabling
   99.9% uptime.
 - Global delivery and fast downloads: Docker leverages Cloudflare's CDN and
-  caching (with Cache Reserve) to achieve cache hit ratios above 99%, reducing
-  reliance on origin traffic and ensuring fast access for developers everywhere.
+  caching (with Cache Reserve) to achieve cache hit ratios more than 99%,
+  reducing reliance on origin traffic and ensuring fast access for developers
+  everywhere.
 - Durability: Docker maintains a documented backup policy and performs full
   daily, backups of production data.
 

content/manuals/docker-hub/repos/manage/trusted-content/insights-analytics.md

@@ -75,22 +75,16 @@ To access the report:
 
 The summary report is a CSV file that contains the following data points:
 
-- `DATE_GRANULARITY`: Weekly or monthly granularity of the data. Indicates
-  whether the data is aggregated by week or month.
-- `DATE_REFERENCE`: The start date of the week or month in YYYY-MM-DD format
-  (e.g., `2025-09-29` for the week starting September 29, 2025).
-- `PUBLISHER_NAME`: The name of the Docker organization that owns the repository
-  (e.g., `demonstrationorg`).
-- `LEVEL`: The aggregation level of the data - either `repository` (summary for
-  entire repository), `tag` (summary for specific tag), or `digest` (summary for
-  specific digest).
-- `REFERENCE`: The specific reference being summarized - the repository name,
-  tag name, or digest hash depending on the level.
-- `DATA_DOWNLOADS`: The number of actual image downloads.
-- `VERSION_CHECKS`: The number of version checks performed (HEAD requests to
-  check for updates without downloading the full image).
-- `EVENT_COUNT`: The total number of events, calculated as the sum of data
-  downloads and version checks.
+| Field | Description |
+|-------|-------------|
+| `DATE_GRANULARITY` | Weekly or monthly granularity of the data. Indicates whether the data is aggregated by week or month. |
+| `DATE_REFERENCE` | The start date of the week or month in YYYY-MM-DD format (e.g., `2025-09-29` for the week starting September 29, 2025). |
+| `PUBLISHER_NAME` | The name of the Docker organization that owns the repository (e.g., `demonstrationorg`). |
+| `LEVEL` | The aggregation level of the data - either `repository` (summary for entire repository), `tag` (summary for specific tag), or `digest` (summary for specific digest). |
+| `REFERENCE` | The specific reference being summarized - the repository name, tag name, or digest hash depending on the level. |
+| `DATA_DOWNLOADS` | The number of actual image downloads. |
+| `VERSION_CHECKS` | The number of version checks performed (HEAD requests to check for updates without downloading the full image). |
+| `EVENT_COUNT` | The total number of events, calculated as the sum of data downloads and version checks. |
 
 ### Trends report
 
@@ -109,35 +103,29 @@ To access the report:
 
 1. Sign in to [Docker Hub](https://hub.docker.com/).
 2. Select **My Hub** in the top navigation.
-3. Select your organiztion in the left navigation.
+3. Select your organization in the left navigation.
 4. Select **Analytics** > **Trends** in the left navigation.
 5. Select **DATA BY WEEK** or **DATA BY MONTH** to choose the data granularity.
 6. Select **Download report** for the desired week or month.
 
 The trends report is a CSV file that contains the following data points:
 
-- `DATE_GRANULARITY`: Weekly or monthly granularity of the data.
-- `DATE_REFERENCE`: The start date of the week or month.
-- `PUBLISHER_NAME`: The name of the organization that owns the repository.
-- `IMAGE_REPOSITORY`: The full name of the image repository (e.g.,
-  `demonstrationorg/scout-demo`).
-- `NAMESPACE`: The Docker organization or namespace that owns the repository.
-- `IP_COUNTRY`: The country code (ISO 3166-1 alpha-2) where the pull request
-  originated from (e.g., `US`, `CA`).
-- `CLOUD_SERVICE_PROVIDER`: The cloud service provider used for the pull request
-  (e.g., `gcp`, `aws`, `azure`) or `no csp` for non-cloud providers.
-- `USER_AGENT`: The client application or tool used to pull the image (e.g.,
-  `docker`, `docker-scout`, `node-fetch`, `regclient`).
-- `TAG`: The specific image tag that was pulled, or `\\N` if no specific tag was
-  used.
-- `DATA_DOWNLOADS`: The number of data downloads for the specified criteria.
-- `VERSION_CHECKS`: The number of version checks (HEAD requests) performed
-  without downloading the full image.
-- `PULLS`: The total number of pull requests (data downloads + version checks).
-- `UNIQUE_AUTHENTICATED_USERS`: The number of unique authenticated users who
-  performed pulls.
-- `UNIQUE_UNAUTHENTICATED_USERS`: The number of unique unauthenticated users who
-  performed pulls.
+| Field | Description |
+|-------|-------------|
+| `DATE_GRANULARITY` | Weekly or monthly granularity of the data. |
+| `DATE_REFERENCE` | The start date of the week or month. |
+| `PUBLISHER_NAME` | The name of the organization that owns the repository. |
+| `IMAGE_REPOSITORY` | The full name of the image repository (e.g., `demonstrationorg/scout-demo`). |
+| `NAMESPACE` | The Docker organization or namespace that owns the repository. |
+| `IP_COUNTRY` | The country code (ISO 3166-1 alpha-2) where the pull request originated from (e.g., `US`, `CA`). |
+| `CLOUD_SERVICE_PROVIDER` | The cloud service provider used for the pull request (e.g., `gcp`, `aws`, `azure`) or `no csp` for non-cloud providers. |
+| `USER_AGENT` | The client application or tool used to pull the image (e.g., `docker`, `docker-scout`, `node-fetch`, `regclient`). |
+| `TAG` | The specific image tag that was pulled, or `\\N` if no specific tag was used. |
+| `DATA_DOWNLOADS` | The number of data downloads for the specified criteria. |
+| `VERSION_CHECKS` | The number of version checks (HEAD requests) performed without downloading the full image. |
+| `PULLS` | The total number of pull requests (data downloads + version checks). |
+| `UNIQUE_AUTHENTICATED_USERS` | The number of unique authenticated users who performed pulls. |
+| `UNIQUE_UNAUTHENTICATED_USERS` | The number of unique unauthenticated users who performed pulls. |
 
 ### Technographic report
 
@@ -159,32 +147,27 @@ To access the report:
 
 1. Sign in to [Docker Hub](https://hub.docker.com/).
 2. Select **My Hub** in the top navigation.
-3. Select your organiztion in the left navigation.
+3. Select your organization in the left navigation.
 4. Select **Analytics** > **Technographic** in the left navigation.
 5. Select **DATA BY WEEK** or **DATA BY MONTH** to choose the data granularity.
 6. Select **Download report** for the desired week or month.
 
 The technographic report is a CSV file that contains the following data points:
 
-- `DATE_GRANULARITY`: Weekly or monthly granularity of the data.
-- `DATE_REFERENCE`: The start date of the week or month in YYYY-MM-DD format.
-- `PUBLISHER_ID`: The unique identifier for the publisher organization.
-- `PUBLISHER_NAME`: The name of the organization that owns the DVP repository.
-- `DVPP_IMAGE`: Your Docker Verified Publisher image repository name.
-- `PAIRED_IMAGE`: The other image repository that is commonly used together with
-  your DVP image.
-- `USERS`: The number of unique users who pulled both your DVP image and the
-  paired image within the time period.
-- `TOTAL_PULLERS`: The total number of unique users who pulled your DVP image
-  during the time period.
-- `PCT_USERS`: The percentage of your image's users who also use the paired
-  image (users/total_pullers).
-- `DOMAINS`: The number of unique company domains that pulled both your DVP
-  image and the paired image.
-- `TOTAL_DOMAINS`: The total number of unique company domains that pulled your
-  DVP image.
-- `PCT_DOMAINS`: The percentage of company domains using your image that also
-  use the paired image (domains/total_domains).
+| Field | Description |
+|-------|-------------|
+| `DATE_GRANULARITY` | Weekly or monthly granularity of the data. |
+| `DATE_REFERENCE` | The start date of the week or month in YYYY-MM-DD format. |
+| `PUBLISHER_ID` | The unique identifier for the publisher organization. |
+| `PUBLISHER_NAME` | The name of the organization that owns the DVP repository. |
+| `DVPP_IMAGE` | Your Docker Verified Publisher image repository name. |
+| `PAIRED_IMAGE` | The other image repository that is commonly used together with your DVP image. |
+| `USERS` | The number of unique users who pulled both your DVP image and the paired image within the time period. |
+| `TOTAL_PULLERS` | The total number of unique users who pulled your DVP image during the time period. |
+| `PCT_USERS` | The percentage of your image's users who also use the paired image (users/total_pullers). |
+| `DOMAINS` | The number of unique company domains that pulled both your DVP image and the paired image. |
+| `TOTAL_DOMAINS` | The total number of unique company domains that pulled your DVP image. |
+| `PCT_DOMAINS` | The percentage of company domains using your image that also use the paired image (domains/total_domains). |
 
 > [!NOTE]
 >
@@ -224,14 +207,14 @@ To access the report:
 The technographic companies report is a CSV file that contains the following
 data points:
 
-- `DATE_GRANULARITY`: Weekly or monthly granularity of the data.
-- `DATE_REFERENCE`: The start date of the week or month in YYYY-MM-DD format.
-- `PUBLISHER_NAME`: The name of the organization that owns the DVP repository.
-- `DOMAIN`: The company domain that pulled both your DVP image and the paired
-  image (e.g., `example.com`).
-- `DVPP_IMAGE`: Your Docker Verified Publisher image repository name.
-- `PAIRED_IMAGE`: The other image repository that was used together with your
-  DVP image by this company.
+| Field | Description |
+|-------|-------------|
+| `DATE_GRANULARITY` | Weekly or monthly granularity of the data. |
+| `DATE_REFERENCE` | The start date of the week or month in YYYY-MM-DD format. |
+| `PUBLISHER_NAME` | The name of the organization that owns the DVP repository. |
+| `DOMAIN` | The company domain that pulled both your DVP image and the paired image (e.g., `example.com`). |
+| `DVPP_IMAGE` | Your Docker Verified Publisher image repository name. |
+| `PAIRED_IMAGE` | The other image repository that was used together with your DVP image by this company. |
 
 Each row represents a unique combination of a company domain, your DVP image,
 and another image that were used together during the specified time period.
@@ -269,33 +252,21 @@ To access the report:
 The tracked companies report is a CSV file that contains the following data
 points:
 
-- `DATE_GRANULARITY`: Weekly or monthly granularity of the data.
-- `DATE_REFERENCE`: The start date of the week or month in YYYY-MM-DD format.
-- `PUBLISHER_NAME`: The name of the organization that owns the DVP repository.
-- `DOMAIN`: The company domain (e.g., `docker.com`) associated with the image
-  pulls.
-- `IP_COUNTRY`: The country code (ISO 3166-1 alpha-2) where the pull request
-  originated from.
-- `CLOUD_SERVICE_PROVIDER`: The cloud service provider used for the pull request
-  or `no csp` for non-cloud providers.
-- `USER_AGENT`: The client application or tool used to pull the image.
-- `INFERRED_USE_CASE`: The inferred deployment environment based on user agent
-  and cloud provider analysis. Values include:
-  - `Local Dev`: Local development environment (e.g., Docker Desktop, direct
-    docker commands)
-  - `CI/CD`: Continuous integration/deployment pipelines (e.g., containerd,
-    build tools, registry mirroring)
-  - `Prod`: Production environments (e.g., Kubernetes, container orchestration
-    platforms)
-  - `Unknown`: Unable to determine the use case from available data
-- `IMAGE_REPOSITORY`: The specific DVP image repository that was pulled.
-- `DATA_DOWNLOADS`: The number of actual image layer downloads for this
-  combination.
-- `VERSION_CHECKS`: The number of version checks (HEAD requests) performed
-  without downloading the full image.
-- `PULLS`: The total number of pull requests (data downloads + version checks).
-- `UNIQUE_AUTHENTICATED_USERS`: The number of unique authenticated users from
-  this domain who performed pulls.
+| Field | Description |
+|-------|-------------|
+| `DATE_GRANULARITY` | Weekly or monthly granularity of the data. |
+| `DATE_REFERENCE` | The start date of the week or month in YYYY-MM-DD format. |
+| `PUBLISHER_NAME` | The name of the organization that owns the DVP repository. |
+| `DOMAIN` | The company domain (e.g., `docker.com`) associated with the image pulls. |
+| `IP_COUNTRY` | The country code (ISO 3166-1 alpha-2) where the pull request originated from. |
+| `CLOUD_SERVICE_PROVIDER` | The cloud service provider used for the pull request or `no csp` for non-cloud providers. |
+| `USER_AGENT` | The client application or tool used to pull the image. |
+| `INFERRED_USE_CASE` | The inferred deployment environment based on user agent and cloud provider analysis. Values include: <br>• `Local Dev`: Local development environment (e.g., Docker Desktop, direct docker commands) <br>• `CI/CD`: Continuous integration/deployment pipelines (e.g., containerd, build tools, registry mirroring) <br>• `Prod`: Production environments (e.g., Kubernetes, container orchestration platforms) <br>• `Unknown`: Unable to determine the use case from available data |
+| `IMAGE_REPOSITORY` | The specific DVP image repository that was pulled. |
+| `DATA_DOWNLOADS` | The number of actual image layer downloads for this combination. |
+| `VERSION_CHECKS` | The number of version checks (HEAD requests) performed without downloading the full image. |
+| `PULLS` | The total number of pull requests (data downloads + version checks). |
+| `UNIQUE_AUTHENTICATED_USERS` | The number of unique authenticated users from this domain who performed pulls. |
 
 > [!NOTE]
 >