Update source build GitHub team name

Documentation/eliminating-pre-builts.md

@@ -143,7 +143,7 @@ contains package information of pre-builts that for one reason or another are
 allowed in the source-build of the repository.
 
 Any new addition to the pre-built exception list must be signed-off by a member
-of the `@dotnet/source-build-internal` team.
+of the `@dotnet/source-build` team.
 
 A common example of a exception that is present in several .NET repositories is
 an [_intermediate

Documentation/sourcebuild-in-repos/new-dependencies.md

@@ -70,15 +70,15 @@ dependency and the nuances it may have.
 1. Is the repo already built in source-build but the specific package is not?
     1. There's probably an issue with source-building this package.  Please talk
       to a [source-build team
-      member](https://github.com/orgs/dotnet/teams/source-build-internal) about
+      member](https://github.com/orgs/dotnet/teams/source-build) about
       why that is and whether we can fix it.
 1. Is this a repo that uses Arcade to build?
     1. Does the foreign repo depend on your repo, directly or indirectly? i.e.
       would adding the dependency create a cycle?
         1. This isn't necessarily a deal-breaker - it can sometimes be worked
           around with reference-only packages.  Please contact a [source-build
           team
-          member](https://github.com/orgs/dotnet/teams/source-build-internal) to
+          member](https://github.com/orgs/dotnet/teams/source-build) to
           discuss.
     1. Does the foreign repo publish to BAR?
         1. If not, please contact them to get them publishing to BAR in an

Documentation/sourcebuild-in-repos/new-repo.md

@@ -61,7 +61,7 @@ MSBuild code that can change the way source build behaves.
 ### `eng/SourceBuildPrebuiltBaseline.xml`
 
 ```xml
-<!-- Whenever altering this or other Source Build files, please include @dotnet/source-build-internal as a reviewer. -->
+<!-- Whenever altering this or other Source Build files, please include @dotnet/source-build as a reviewer. -->
 <!-- See https://aka.ms/dotnet/prebuilts for guidance on what pre-builts are and how to eliminate them. -->
 
 <UsageData>
@@ -86,7 +86,7 @@ Add the source build team as the
 of the source build infrastructure.
 
 ``` text
-/eng/SourceBuild* @dotnet/source-build-internal
+/eng/SourceBuild* @dotnet/source-build
 ```
 
 ### Trying it out locally
@@ -247,7 +247,7 @@ To opt in:
 #### End result
 
 Submit the changes above in a PR and include
-[@source-build-internal](https://github.com/orgs/dotnet/teams/source-build-internal)
+[@source-build](https://github.com/orgs/dotnet/teams/source-build)
 as a reviewer. The jobs (or job, if managed-only) are automatically be added to
 CI in the existing pipeline alongside existing jobs, with a name like `Build
 Source-Build (<Platform>)`:
@@ -355,7 +355,7 @@ flow into `dotnet/installer`, a complete .NET product can be built from source.
 The repository will be synchronized into the VMR during the first build and the
 VMR will be built. This will validate that no prebuilts were added to the system
 and everything is functioning correctly. Please notify
-[@source-build-internal](https://github.com/orgs/dotnet/teams/source-build-internal)
+[@source-build](https://github.com/orgs/dotnet/teams/source-build)
 to be on the lookout for the new repo and they will validate as necessary.
 
 ## Additional resources

Documentation/sourcebuild-in-repos/update-dependencies.md

@@ -12,7 +12,7 @@ branch (e.g. runtime release/6.0 to sdk release/6.0.1xx, release/6.0.2xx, etc).
 Package versions that you are updating to should be source-built in their
 respective repos.  If the version you need is produced in a branch that is not
 yet source-build-compatible please let the [source-build
-team](https://github.com/orgs/dotnet/teams/source-build-internal) know.
+team](https://github.com/orgs/dotnet/teams/source-build) know.
 
 Another common error we see is updating eng/Versions.props but not
 eng/Version.Details.xml.  This causes problems for source-build because we