clarified PAT

Author: dlepow

articles/container-registry/container-registry-tasks-overview.md

@@ -56,7 +56,7 @@ ACR Tasks supports the following triggers when you set a Git repo as the task's
 | Commit | Yes |
 | Pull request | No |
 
-To configure the trigger, you provide the task a personal access token (PAT) to set the webhook in the public or private GitHub or Azure DevOps repo.
+To configure a source code update trigger, you need to provide the task a personal access token (PAT) to set the webhook in the public or private GitHub or Azure DevOps repo.
 
 > [!NOTE]
 > Currently, ACR Tasks doesn't support commit or pull request triggers in GitHub Enterprise repos.
@@ -120,6 +120,9 @@ The following table shows a few examples of supported context locations for ACR
 | Azure DevOps subfolder | Files within a subfolder in a public or private Azure repo. Example shows combination of branch and subfolder specification. | `https://dev.azure.com/user/myproject/_git/myapp-repo#mybranch:myfolder` |
 | Remote tarball | Files in a compressed archive on a remote webserver. | `http://remoteserver/myapp.tar.gz` |
 
+> [!NOTE]
+> When using a private a Git repo as a context for a task, you need to provide a personal access token (PAT).
+
 ## Image platforms
 
 By default, ACR Tasks builds images for the Linux OS and the amd64 architecture. Specify the `--platform` tag to build Windows images or Linux images for other architectures. Specify the OS and optionally a supported architecture in OS/architecture format (for example, `--platform Linux/arm`). For ARM architectures, optionally specify a variant in OS/architecture/variant format (for example, `--platform Linux/arm64/v8`):