Make images accessible in images/enterprise/ subdirectories Mi-Or (#34812)

Co-authored-by: Laura Coursen <lecoursen@github.com>

content/admin/configuration/configuring-network-settings/configuring-the-ip-address-using-the-virtual-machine-console.md

@@ -23,7 +23,5 @@ shortTitle: Set the IP using the console
 
 {% data reusables.enterprise_installation.open-vm-console-start %}
 3. Choose to configure the `IPv4` or `IPv6` protocol.
-  ![Options to choose the IPv4 or the IPv6 protocol](/assets/images/enterprise/network-configuration/IPv4-or-IPv6-protocol.png)
 4. Configure options for the protocol you chose.
-  ![Menu with IP protocol options](/assets/images/enterprise/network-configuration/network-settings-selection.png)
 {% data reusables.enterprise_installation.vm-console-done %}

content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/migrating-from-github-enterprise-1110x-to-2123.md

@@ -50,12 +50,9 @@ To upgrade to the latest version of {% data variables.product.prodname_enterpris
 2. In a browser, navigate to the new replica appliance's IP address and upload your {% data variables.product.prodname_enterprise %} license.
 3. Set an admin password.
 5. Click **Migrate**.
-![Choosing install type](/assets/images/enterprise/migration/migration-choose-install-type.png)
+6. In the "Add new SSH key" text field, paste your backup host access SSH key.
-6. Paste your backup host access SSH key into "Add new SSH key".
-![Authorizing backup](/assets/images/enterprise/migration/migration-authorize-backup-host.png)
 7. Click **Add key** and then click **Continue**.
 8. Copy the `ghe-restore` command that you'll run on the backup host to migrate data to the new instance.
-![Starting a migration](/assets/images/enterprise/migration/migration-restore-start.png)
 9. Enable maintenance mode on the old instance and wait for all active processes to complete. For more information, see "[AUTOTITLE](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode)."
 
   {% note %}
@@ -87,9 +84,7 @@ To upgrade to the latest version of {% data variables.product.prodname_enterpris
   ```
 
 12. Return to the new instance's restore status screen to see that the restore completed.
-![Restore complete screen](/assets/images/enterprise/migration/migration-status-complete.png)
 13. Click **Continue to settings** to review and adjust the configuration information and settings that were imported from the previous instance.
-![Review imported settings](/assets/images/enterprise/migration/migration-status-complete.png)
 14. Click **Save settings**.
 
   {% note %}

content/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md

@@ -58,9 +58,7 @@ An organization administrator can only configure hook permissions for an organiz
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 4. In the left sidebar, click **Hooks**.
-![Hooks sidebar](/assets/images/enterprise/orgs-and-teams/hooks-sidebar.png)
+5. Next to the pre-receive hook that you want to configure, select the **Hook permissions** dropdown menu, then click an option.
-5. Next to the pre-receive hook that you want to configure, click the **Hook permissions** drop-down menu. Select whether to enable or disable the pre-receive hook, or allow it to be configured by the repository administrators.
-![Hook permissions](/assets/images/enterprise/orgs-and-teams/hook-permissions.png)
 
 ## Configure pre-receive hooks for a repository
 

content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md

@@ -57,8 +57,7 @@ You must be a site admin and an organization owner to create a team with LDAP sy
 {% data reusables.user-settings.access_org %}
 {% data reusables.organizations.new_team %}
 {% data reusables.organizations.team_name %}
-6. Search for an LDAP group's DN to map the team to. If you don't know the DN, type the LDAP group's name. {% data variables.product.prodname_ghe_server %} will search for and autocomplete any matches.
+6. Under "LDAP group", search for an LDAP group's DN to map the team to. If you don't know the DN, type the LDAP group's name. {% data variables.product.prodname_ghe_server %} will search for and autocomplete any matches.
-![Mapping to the LDAP group DN](/assets/images/enterprise/orgs-and-teams/ldap-group-mapping.png)
 {% data reusables.organizations.team_description %}
 {% data reusables.organizations.team_visibility %}
 {% data reusables.organizations.create-team-choose-parent %}

content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md

@@ -19,23 +19,11 @@ shortTitle: Project management with Jira
 ---
 ## Connecting Jira to a {% data variables.product.prodname_enterprise %} organization
 
-1. Sign into your {% data variables.product.prodname_enterprise %} account at http[s]://[hostname]/login. If already signed in, click on the {% data variables.product.prodname_dotcom %} logo in the top left corner.
+1. Sign into your {% data variables.product.prodname_enterprise %} account at `http[s]://[hostname]/login`. If already signed in, click on the {% data variables.product.prodname_dotcom %} logo in the top left corner.
 2. Click on your profile icon under the {% data variables.product.prodname_dotcom %} logo and select the organization you would like to connect with Jira.
-
-  ![Select an organization](/assets/images/enterprise/orgs-and-teams/profile-select-organization.png)
-
 3. Click on the **Edit _organization name_ settings** link.
-
-  ![Edit organization settings](/assets/images/enterprise/orgs-and-teams/edit-organization-settings.png)
-
 4. In the left sidebar, under **Developer settings**, click **OAuth Apps**.
-
-  ![Select OAuth Apps](/assets/images/enterprise/orgs-and-teams/organization-dev-settings-oauth-apps.png)
-
 5. Click on the **Register new application** button.
-
-  ![Register new application button](/assets/images/enterprise/orgs-and-teams/register-oauth-application-button.png)
-
 6. Fill in the application settings:
     - In the **Application name** field, type "Jira" or any name you would like to use to identify the Jira instance.
     - In the **Homepage URL** field, type the full URL of your Jira instance.
@@ -47,17 +35,8 @@ shortTitle: Project management with Jira
 
 1. On your Jira instance, log into an account with administrative access.
 2. At the top of the page, click the settings (gear) icon and choose **Applications**.
-
-  ![Select Applications on Jira settings](/assets/images/enterprise/orgs-and-teams/jira/jira-applications.png)
-
 3. In the left sidebar, under **Integrations**, click **DVCS accounts**.
-
-  ![Jira Integrations menu - DVCS accounts](/assets/images/enterprise/orgs-and-teams/jira/jira-integrations-dvcs.png)
-
 4. Click **Link Bitbucket Cloud or {% data variables.product.prodname_dotcom %} account**.
-
-  ![Link GitHub account to Jira](/assets/images/enterprise/orgs-and-teams/jira/jira-link-github-account.png)
-
 5. In the **Add New Account** modal, fill in your {% data variables.product.prodname_enterprise %} settings:
     - From the **Host** dropdown menu, choose **{% data variables.product.prodname_enterprise %}**.
     - In the **Team or User Account** field, type the name of your {% data variables.product.prodname_enterprise %} organization or user account.

content/organizations/managing-user-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md

@@ -28,7 +28,9 @@ If your organization [requires members to use two-factor authentication](/organi
 {% data reusables.organizations.people %}
 {% data reusables.organizations.people_tab_outside_collaborators %}
 {% ifversion fpt or ghec %}
-5. To the right of the name of the outside collaborator you want to become a member, use the {% octicon "gear" aria-label="The gear icon" %} drop-down menu and click **Invite to organization**.![Invite outside collaborators to organization](/assets/images/help/organizations/invite_outside_collaborator_to_organization.png)
+5. To the right of the name of the outside collaborator you want to become a member, select the {% octicon "kebab-horizontal" aria-label="Collaborator settings" %} dropdown menu and click **Invite to organization**. 
+
+   ![Invite outside collaborators to organization](/assets/images/help/organizations/invite_outside_collaborator_to_organization.png)
 {% else %}
 5. To the right of the name of the outside collaborator you want to become a member, click **Invite to organization**.![Invite outside collaborators to organization](/assets/images/enterprise/orgs-and-teams/invite_outside_collabs_to_org.png)
 {% endif %}

data/reusables/audit_log/octicon_icon.md

@@ -1,2 +1 @@
-1. In the upper-left corner of any page, click <span aria-label="the Octocat icon" class="octicon octicon-mark-github"></span>.
+1. In the upper-left corner of any page, click {% octicon "mark-github" aria-label="Global navigation" %}.
-![Octocat icon](/assets/images/enterprise/navigation/octocat-icon.png)

data/reusables/enterprise_installation/open-vm-console-start.md

@@ -1,3 +1,2 @@
 1. Using your virtualization platform tools, open the virtual machine console.
-  ![{% data variables.product.prodname_enterprise %} console](/assets/images/enterprise/network-configuration/virtual-machine-console.png)
 2. To start your network setup, press **S**.