Remove outdated mention of sharing SMTP credentials with GitHub for GitHub AE email configuration (#18877)

Author: mattpollard

content/admin/configuration/about-enterprise-configuration.md

@@ -17,9 +17,7 @@ topics:
 {% endif %}
 
 {% if currentVersion == "github-ae@latest" %}
-The first time you access your enterprise, you will complete an initial configuration to get {% data variables.product.product_name %} ready to use. The initial configuration includes connecting your enterprise with an idP, authenticating with SAML SSO, and configuring policies for repositories and organizations in your enterprise. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)."
-
-For users to receive any emails from {% data variables.product.product_name %} after the initial configuration, you must ask {% data variables.contact.github_support %} to configure outbound email support with your SMTP server. For more information, see "[Configuring email for notifications](/admin/configuration/configuring-email-for-notifications)."
+The first time you access your enterprise, you will complete an initial configuration to get {% data variables.product.product_name %} ready to use. The initial configuration includes connecting your enterprise with an identity provider (IdP), authenticating with SAML SSO, configuring policies for repositories and organizations in your enterprise, and configuring SMTP for outbound email. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)."
 
 Later, you can use the site admin dashboard and enterprise settings to further configure your enterprise, manage users, organizations and repositories, and set policies that reduce risk and increase quality. 
 
@@ -29,4 +27,4 @@ All enterprises are configured with subdomain isolation and support for TLS 1.2
 ### Further reading
 
 - "[Managing users, organizations, and repositories](/admin/user-management)"
-- "[Setting policies for your enterprise](/admin/policies)"
+- "[Setting policies for your enterprise](/admin/policies)"

content/admin/configuration/initializing-github-ae.md

@@ -103,11 +103,11 @@ Once this is initialized, you can reconfigure any settings after the initializat
  settings to allow incoming emails](/admin/configuration/configuring-email-for-notifications#configuring-dns-and-firewall-settings-to-allow-incoming-emails)."
   !["Enable" checkbox for email settings configuration](/assets/images/enterprise/configuration/ae-enable-email-configure.png)
 3. Complete your email server settings:
-  - In the **Server address** field, type the address of your SMTP server.
-  - In the **Port** field, type the port that your SMTP server uses to send email.
-  - In the **Domain** field, type the domain name that your SMTP server will send with a HELO response, if any.
-  - In the **Authentication** dropdown, choose the type of encryption used by your SMTP server.
-  - In the **No-reply email address** field, type the email address to use in the From and To fields for all notification emails.
+    - In the **Server address** field, type the address of your SMTP server.
+    - In the **Port** field, type the port that your SMTP server uses to send email.
+    - In the **Domain** field, type the domain name that your SMTP server will send with a HELO response, if any.
+    - In the **Authentication** dropdown, choose the type of encryption used by your SMTP server.
+    - In the **No-reply email address** field, type the email address to use in the From and To fields for all notification emails.
 
 4. If you want to discard all incoming emails that are addressed to the no-reply email address, select **Discard email addressed to the no-reply email address**.
   !["Discard" checkbox for email settings configuration](/assets/images/enterprise/configuration/ae-discard-email.png)