fix typo

www/DirectMapping.md

@@ -20,12 +20,14 @@ JNA supports a direct mapping method which can improve performance substantially
         }
     }
 
-Direct mapping supports the same type mappings as interface mapping, except for arrays of `Pointer`/`Structure`/`String`/`WString`/`NativeMapped` as function arguments.  **Varargs are not supported**.
+Direct mapping supports the same type mappings as interface mapping, except for arrays of `Pointer`/`Structure`/`String`/`WString`/`NativeMapped` as function arguments.  
+
+**Varargs are not supported**.
 
 Methods may be either static or member methods; the class or object is ignored on the native side.
 
 You can easily convert from interface mapping to direct mapping by creating a direct mapping class which implements your library interface, with all methods defined as native methods. Then your library instance variable can be assigned an instance of this new class instead of the object returned by `Native.loadLibrary()`.
 
-If you are using a profile which rewrites native methods, you may need to
+If you are using a profiler which rewrites native methods, you may need to
 set the system property `jna.profiler.prefix` to the prefix used by the
 profiler to avoid linkage errors when binding to native methods.