docs: expose self-service fork detachment for fpt/ghec users (#60628)

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: crwaters16 <78226508+crwaters16@users.noreply.github.com>
Co-authored-by: Anne-Marie <102995847+am-stead@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Author: 4 people

content/pull-requests/collaborating-with-pull-requests/working-with-forks/detaching-a-fork.md

@@ -10,7 +10,7 @@ category:
   - Work with forks
 ---
 
-{% ifversion ghes > 3.16 %}
+{% ifversion fpt or ghec or ghes > 3.16 %}
 
 ## Converting a fork into a standalone repository
 
@@ -21,9 +21,13 @@ To turn your fork into a standalone repository, you can leave the fork network e
 > * All git commit metadata will be preserved. Commits may become eligible to be counted as contributions if they meet certain criteria. For more information, see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account).
 > * Leaving the fork network is **permanent** and the new repository **cannot** be reconnected to the fork network.
 
+{% ifversion ghes %}
+
 > [!NOTE]
 > If you are unable to detach a fork, contact your site administrator.
 
+{% endif %}
+
 ## Leaving the fork network
 
 You can only detach forks with the leave network option when:
@@ -42,7 +46,7 @@ While the fork is being detached, some operations will be briefly unavailable un
 
 {% endif %}
 
-## Manually Leaving the fork network
+## Manually leaving the fork network
 
 To turn your fork into a standalone repository, you can clone the fork, use the clone to create a new repository, and then delete the fork removing the connection to the original network.