Merge pull request #6064 from davidmrdavid/dev/dajusto/clarify-hotpatch-docs

Clarify that `/hotpatch` is only available in x86 targets

Author: JamesJBarnett

docs/build/reference/hotpatch-create-hotpatchable-image.md

@@ -1,35 +1,36 @@
 ---
-description: "Learn more about: /hotpatch (Create Hotpatchable Image)"
-title: "/hotpatch (Create Hotpatchable Image)"
-ms.date: "12/7/2021"
+description: "Learn more about: /hotpatch (Create hotpatchable image)"
+title: "/hotpatch (Create hotpatchable image)"
+ms.date: "9/4/2025"
 f1_keywords: ["/hotpatch", "VC.Project.VCCLCompilerTool.CreateHotpatchableImage"]
-helpviewer_keywords: ["hot patching", "-hotpatch compiler option [C++]", "/hotpatch compiler option [C++]", "hotpatching"]
-ms.assetid: aad539b6-c053-4c78-8682-853d98327798
+helpviewer_keywords: ["hot patching", "hotpatching", "-hotpatch compiler option [C++]", "/hotpatch compiler option [C++]"]
 ---
-# /hotpatch (Create Hotpatchable Image)
+# /hotpatch (Create hotpatchable image)
 
-Prepares an image for hot patching.
+Prepares an image for hotpatching.
 
 ## Syntax
 
 ```
 /hotpatch
 ```
 
+> [!NOTE]
+> This option is only available for x86
+
 ## Remarks
 
-When **/hotpatch** is used in a compilation, the compiler ensures that the first instruction of each function is at least two bytes, and no jump within the function goes to the first instruction. These conditions are required for hot patching.
+When `/hotpatch` is used during compilation, the compiler ensures that the first instruction of each function is at least 2 bytes long and that no jump within the function goes to the first instruction. These conditions are required for hotpatching.
 
-To complete the preparation for making an image hotpatchable, after you use **/hotpatch** to compile, you must use [/FUNCTIONPADMIN (Create Hotpatchable Image)](functionpadmin-create-hotpatchable-image.md) to link. When you compile and link an image by using one invocation of cl.exe, **/hotpatch** implies **/functionpadmin**.
+To complete the preparation for making an image hotpatchable, after you compile with `/hotpatch`, use [`/functionpadmin`](functionpadmin-create-hotpatchable-image.md) to link. When you compile and link an image using one invocation of `cl.exe`, `/hotpatch` implies `/functionpadmin`.
 
-Because instructions are always two bytes or larger on the ARM architecture, and because x64 compilation is always treated as if **/hotpatch** has been specified, you don't have to specify **/hotpatch** when you compile for these targets; however, you must still link by using **/functionpadmin** to create hotpatchable images for them. The **/hotpatch** compiler option only affects x86 compilation.
+> [!TIP]
+> Arm64 and x64 architectures are always treated as hotpatchable. But you must still link by using `/functionpadmin` to create hotpatchable images for them.
 
 ### To set this compiler option in the Visual Studio development environment
 
 1. Open the project's **Property Pages** dialog box. For details, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
-
 1. Select the **Configuration Properties** > **C/C++** > **Command Line** property page.
-
 1. Add the compiler option to the **Additional Options** box.
 
 ### To set this compiler option programmatically
@@ -38,5 +39,5 @@ Because instructions are always two bytes or larger on the ARM architecture, and
 
 ## See also
 
-[MSVC Compiler Options](compiler-options.md)<br/>
+[MSVC Compiler Options](compiler-options.md)\
 [MSVC Compiler Command-Line Syntax](compiler-command-line-syntax.md)