--- wikisrc/features/uvm_hotplug.mdwn	2016/12/29 17:02:27	1.3
+++ wikisrc/features/uvm_hotplug.mdwn	2019/04/08 23:30:45	1.5
@@ -22,8 +22,8 @@
 
   2. What files may be affected?
 
-     In most of the architectures the "sys/arch/<arch_name>/<arch_name>/machdep.c"
-     and "sys/arch/<arch_name>/<arch_name>/pmap.c" if they exist are usually
+     In most of the architectures the `sys/arch/<arch_name>/<arch_name>/machdep.c`
+     and `sys/arch/<arch_name>/<arch_name>/pmap.c` if they exist are usually
      affected.
 
      But this may not be a exhaustive list. Any other files that deals with pmap and
@@ -31,7 +31,7 @@
 
   3. What does it do ?
 
-     [[!template id=man name=uvm_hotplug section=9]] manages the previously exposed "vm_physmem" static array which
+     [[!template id=man name=uvm_hotplug section=9]] manages the previously exposed `vm_physmem` static array which
      used to keep track of the memory segments.
 
      In the current implementation, the array has been replaced with a
@@ -40,7 +40,7 @@
 
      An array based implementation is also provided, for backwards
      compatibility. This is the default implementation and does not provide
-     hot pluggability. It is also used without 'options UVM_HOTPLUG'
+     hot pluggability. It is also used without `options UVM_HOTPLUG`
      However the API itself is implementation agnostic.
 
   4. Why is it needed?
@@ -62,4 +62,4 @@
 
      An example of [[!template id=man name=uvm_hotplug section=9]] api's
      application can be found in
-     [[!template id=man name=balloon section=4]].
\ No newline at end of file
+     [[!template id=man name=balloon section=4]].