Update docs (#6983)

Author: nkolev92

CONTRIBUTING.md

@@ -33,7 +33,7 @@ For more information, see the [.NET Foundation Code of Conduct](https://dotnetfo
     - Keep the pull request template, and link to an issue.
     - Use a meaningful PR title, not the auto-generated title based on the branch name.
     - All PRs created by someone outside the NuGet team will be assigned the `Community` label, and a team member will be assigned as the PR shepherd, who will be responsible for making sure the PR gets reviewed (even if they don't review it themselves), and periodically check the PR for progress.
-      - PRs from forks do not trigger CI automatically. Someone in the team needs to apply the "Approved for CI", which will build only the current commit. If changes are pushed to the branch, the "Approved for CI" label needs to be removed and re-applied.
+      - PRs from forks trigger the test pipeline automatically, but not the PrivateDev pipeline. Someone in the team needs to trigger the pipeline manually.
     - If the NuGet team requests changes and the PR author does not respond within 1 month, a reminder will be added. If no action is taken within 2 months of the reminder, the PR will be closed due to inactivity.
 1. _One-time_: Sign the contributor license agreement, if you haven't signed it before. The [.NET Foundation Bot](https://github.com/dnfclas) will comment on the pull request you just created and guide you on how to sign the CLA.
 1. Submit a doc pull request to the [docs.microsoft-com.nuget](https://github.com/NuGet/docs.microsoft.com-nuget/) repo, if this is a new feature or behavior change.