From 016b25de9d70517183943358d2877797b35a9f59 Mon Sep 17 00:00:00 2001 From: Craig Osterhout <103533812+craig-osterhout@users.noreply.github.com> Date: Fri, 23 Feb 2024 10:43:25 -0800 Subject: [PATCH] update oras link (#19496) Signed-off-by: Craig Osterhout --- content/docker-hub/oci-artifacts.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/content/docker-hub/oci-artifacts.md b/content/docker-hub/oci-artifacts.md index 76201571e6..00e3d241de 100644 --- a/content/docker-hub/oci-artifacts.md +++ b/content/docker-hub/oci-artifacts.md @@ -37,9 +37,10 @@ You manage OCI artifacts on Docker Hub in a similar way you would container images. Pushing and pulling OCI artifacts to and from a registry is done using a -registry client. [ORAS CLI](https://oras.land/cli/) is a command-line tool that -provides the capability of managing OCI artifacts in a registry. If you use Helm -charts, the [Helm CLI](https://helm.sh/docs/intro/install/) provides built-in +registry client. [ORAS CLI](https://oras.land/docs/installation) +is a command-line tool that provides the capability of managing +OCI artifacts in a registry. If you use Helm charts, the +[Helm CLI](https://helm.sh/docs/intro/install/) provides built-in functionality for pushing and pulling charts to and from a registry. Registry clients invoke HTTP requests to the Docker Hub registry API. The