Remove mentions of the core team.

This updates documentation to point to the leadership council.

Author: ehuss

src/community/survey-faq.md

@@ -27,7 +27,7 @@ The answers from the survey will be anonymized, aggregated, and summarized. A hi
 
 ### How is personally identifiable information handled?
 
-Nearly every question in the survey is optional. You are welcome to share as much or as little information as you are comfortable with. Only the Rust language Core Team and the Community Team Survey Leads will have access to the raw data from the survey. All the answers are anonymized prior to be shared with the rest of the teams and prior to the results publication.
+Nearly every question in the survey is optional. You are welcome to share as much or as little information as you are comfortable with. Only the Community Team Survey Leads will have access to the raw data from the survey. All the answers are anonymized prior to be shared with the rest of the teams and prior to the results publication.
 
 ### Why is the survey collecting contact information?
 
@@ -39,7 +39,7 @@ The survey optionally collects contact information for the following cases if yo
 - Rust training
 - interest in a Rust team contacting you about your survey responses
 
-If you would like to be contacted about any of this, or any other concerns, but you don't want to associate your email with your survey responses, you can instead email the Rust Community Team at community-team@rust-lang.org or the Core Team at core-team@rust-lang.org, and we will connect you to the right people.
+If you would like to be contacted about any of this, or any other concerns, but you don't want to associate your email with your survey responses, you can instead email the Rust Community Team at community-team@rust-lang.org, and we will connect you to the right people.
 
 ## Where and when is the survey results report published?
 

src/crates-io/crate-removal.md

@@ -4,8 +4,8 @@ If we get a DMCA takedown notice, here's what needs to happen:
 
 ## Contact Legal
 
-Before removing the crates, get in touch with legal support, currently by
-emailing the Core team, and ask an opinion from them on the received request and
+Before removing the crates, get in touch with legal support,
+and ask an opinion from them on the received request and
 whether we have to comply with it.
 
 ## Remove relevant version(s) and/or entire crates from crates.io

src/infra/docs/dns.md

@@ -156,7 +156,7 @@ transfer a domain name to the Rust project's registrar:
 
 1. Ask inside the infrastructure team if this is a domain name the project
    wants to own. In some more complicated cases this will need to be escalated
-   to the core team.
+   to the Leadership Council.
 
 2. If the domain name doesn’t already use AWS Route 53 as its nameserver, ask
    the current owner of the domain a list of all the DNS records that will need

src/infra/docs/sentry.md

@@ -21,7 +21,7 @@ If you're a member of a Rust Team and you want to use Sentry for a project your
 team manages, you need to follow these steps:
 
 1. If the project is public facing (i.e. people outside the team are supposed
-   to access it) you need to contact the Core team to request support in
+   to access it) you need to contact the Leadership Council to request support in
    amending the privacy policy, adding a note that your service is using Sentry
    too similar to the existing ones.
 

src/platforms/blogs.md

@@ -46,15 +46,15 @@ much context. Posts on the team blog can assume a lot more context and familiari
 
 ## Writing for the Main Rust blog
 
-The core team ultimately decides what to post on the main Rust blog.
+The Leadership Council ultimately decides what to post on the main Rust blog.
 
 Post proposals describing exciting developments from within the Rust org are welcome, as well as
 posts that describe exciting applications of Rust. We do not generally do “promotional
 cross-posting” with other projects, however.
 
-If you would like to propose a blog post for the main blog, please reach out to a [core team
-member](https://www.rust-lang.org/governance/teams/core). It is not suggested to just open PRs
-against the main Rust blog that add posts without first discussing it with a core team member.
+If you would like to propose a blog post for the main blog,
+please reach out to a [Leadership Council member](https://www.rust-lang.org/governance/teams/leadership-council).
+It is not suggested to just open PRs against the main Rust blog that add posts without first discussing it with a Leadership Council member.
 
 ### Release note blog posts
 

src/platforms/github.md

@@ -23,13 +23,11 @@ of its discussions.
 
 > Who administrates the `rust-lang` organisation?
 
-All core team members have the `admin` role.
+The infrastructure team is responsible for administrating the GitHub organization.
 
 > How do I create a new repository under the `rust-lang` organisation, or make
   changes that require `admin` level permissions?
 
-You can contact a GitHub admin directly, or post the request in [`project leads
-(public)`] stream on Zulip and an admin will be able to respond to your request
-there.
+New repositories may be created by submitting a PR to add the repository in the [Rust team database][teams].
 
-[`project leads (public)`]: https://rust-lang.zulipchat.com/#narrow/stream/217588-project-leads.20(public)
+[teams]: https://github.com/rust-lang/team