clarify consideration

website/docs/docs/build/packages.md

@@ -165,11 +165,12 @@ dbt Cloud supports private packages from [supported](#prerequisites) Git repos l
 
 #### Prerequisites
 
-To use native private packages, you must have one of the following Git providers configured in the **Integrations** section of your **Account settings**:
-- [GitHub](/docs/cloud/git/connect-github)
-- [Azure DevOps](/docs/cloud/git/connect-azure-devops)
-- Support for GitLab is coming soon.
-
+- To use native private packages, you must have one of the following Git providers configured in the **Integrations** section of your **Account settings**:
+  - [GitHub](/docs/cloud/git/connect-github)
+  - [Azure DevOps](/docs/cloud/git/connect-azure-devops)
+    - For Azure DevOps, use the `org/repo` path (not the `org_name/project_name/repo_name` path) with the project tier inherited from the integrated source repository.
+    - Private packages only work within a single Azure DevOps project. If your repositories are in different projects within the same organization, you can't reference them in the `private` key at this time.
+  - Support for GitLab is coming soon.
 
 #### Configuration
 
@@ -188,7 +189,10 @@ packages:
 </File>
 
 :::tip Azure DevOps considerations
-Currently, the private package feature only works when the ADO package repository is within the same project as your source repository. Normally ADO repos use the `org_name/project_name/repo_name` path. However, private package supports only the `org/repo` path. 
+
+- Private packages currently only work if the package repository is in the same Azure DevOps project as the source repo.
+- Use the `org/repo` path (not the normal ADO `org_name/project_name/repo_name` path) in the `private` key. 
+- Repositories in different Azure DevOps projects is currently not supported until a future update.
 
 You can use private packages by specifying `org/repo` in the `private` key:
 
@@ -201,12 +205,6 @@ packages:
 </File>
 :::
 
-For Azure DevOps repositories, you can only specify the `org/repo` path. The project tier is inherited from the source repository currently integrated with dbt Cloud.
-
-- If the package repository is within the same project as your source repository, you’re in the clear. Simply specify org/repo in the private block.
-- If the package repository is not within the same project as your source repository, this feature will not work for you until a future update.
-- This currently only works within a single Azure DevOps project. If your repositories are in different projects within the same organization, you can't reference them in the `private` key at this time.
-
 You can pin private packages similar to regular dbt packages:
 
 ```yaml