Update detaching-a-fork.md (#55435)

Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com>

Author: patrick-knight

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

@@ -10,6 +10,8 @@ topics:
 permissions: People with admin access for a forked repository can delete the forked repository.
 ---
 
+{% ifversion ghes > 3.16 %}
+
 ## Converting a fork into a standalone repository
 
 To turn your fork into a standalone repository, you can leave the fork network ensuring the new repository will no longer automatically sync with changes from the original repository. This is useful when you want to take the work you are doing in a different direction or maintain distinct versions.
@@ -42,6 +44,8 @@ You can only detach forks with the leave network option when:
 
 While the fork is being detached, some operations will be briefly unavailable until the fork has been transitioned to a standalone repository.
 
+{% endif %}
+
 ## 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.