diff --git a/doc/security-guide/ch052_devices.xml b/doc/security-guide/ch052_devices.xml
index dbbe3f7510..551da5deb8 100644
--- a/doc/security-guide/ch052_devices.xml
+++ b/doc/security-guide/ch052_devices.xml
@@ -75,7 +75,7 @@
 </itemizedlist>
         <para>Putting this all together, and adding in some additional useful protections, we recommend the following compiler options for gcc when compiling QEMU:</para>
         <screen>
-CFLAGS="-arch x86_64 -fstack-protector-all -Wstack-protector --param ssp-buffer-size=4 -pie -fPIE -ftrapv -­D_FORTIFY_SOURCE=2 ­O2 -Wl,-z,relro,-z,now"</screen>
+CFLAGS="-arch x86_64 -fstack-protector-all -Wstack-protector --param ssp-buffer-size=4 -pie -fPIE -ftrapv -D_FORTIFY_SOURCE=2 -O2 -Wl,-z,relro,-z,now"</screen>
         <para>We recommend testing your QEMU executable file after it is compiled to ensure that the compiler hardening worked properly.</para>
         <para>Most cloud deployments will not want to build software such as QEMU by hand. It is better to use packaging to ensure that the process is repeatable and to ensure that the end result can be easily deployed throughout the cloud. The references below provide some additional details on applying compiler hardening options to existing packages.</para>
         <itemizedlist><listitem>