Replace 'otp_build patch_app' with 'otp_patch_apply'

1 files changed, 5 insertions, 6 deletions

diff --git a/system/doc/system_principles/versions.xml b/system/doc/system_principles/versions.xml
index 2bf0d18010..c63913d867 100644
--- a/system/doc/system_principles/versions.xml
+++ b/system/doc/system_principles/versions.xml
@@ -61,14 +61,13 @@
     <c>filename:join([<seealso marker="kernel:code#root_dir/0">code:root_dir()</seealso>, "releases", <seealso marker="erts:erlang#system_info_otp_release">erlang:system_info(otp_release)</seealso>, "OTP_VERSION"]).</c></p>
     <p>If the version read from the <c>OTP_VERSION</c> file in a
     development system has a <c>**</c> suffix, the system has been
-    patched using the
-    <seealso marker="doc/installation_guide:PATCH-APP"><c>$ERL_TOP/otp_build patch_app</c></seealso>
-    tool. In this case, the system consists of application versions from
-    multiple OTP versions. The version preceding the <c>**</c>
+    patched using the <c>otp_patch_apply</c> tool available to
+    licensed customers. In this case, the system consists of application
+    versions from multiple OTP versions. The version preceding the <c>**</c>
     suffix corresponds to the OTP version of the base system that
     has been patched. Note that if a development system is updated by
-    other means than <c>$ERL_TOP/otp_build patch_app</c>, the
-    <c>OTP_VERSION</c> file may identify wrong OTP version.</p>
+    other means than <c>otp_patch_apply</c>, the <c>OTP_VERSION</c> file
+    may identify wrong OTP version.</p>
 
     <p>No <c>OTP_VERSION</c> file will be placed in a
     <seealso marker="create_target">target system</seealso> created