Doc++

doc/platforms-windows.dox

@@ -36,10 +36,10 @@ namespace Magnum {
 
 Windows supports two approaches to advertising HiDPI support. The recommended
 way is via a so-called manifest file added to an executable, but it's also
-possible to it programatically through the `SetProcessDpiAwareness()` family of
+possible to it programatically through the [SetProcessDpiAwareness()](https://docs.microsoft.com/en-us/windows/win32/api/shellscalingapi/nf-shellscalingapi-setprocessdpiawareness)
-APIs. Note there's three different levels of DPI awareness setup for Windows
+family of APIs. Note there's three different levels of DPI awareness setup for
-Vista and newer, Windows 8.1 and newer and Windows 10, and for best support may
+Windows Vista and newer, Windows 8.1 and newer and Windows 10, and for best
-want to support all three.
+support may want to support all three.
 
 When using MSVC, the manifest file can be added directly via CMake. Advertising application-wide per-monitor support can look like in the following snippet,
 together with fallbacks for older systems:

src/Magnum/Math/Range.h

@@ -225,7 +225,7 @@ template<UnsignedInt dimensions, class T> class Range {
         }
 
         /**
-         * @brief Padded rage
+         * @brief Padded range
          *
          * Translates the minimal and maximal coordinates by given amount.
          * Center remains the same.

src/Magnum/Mesh.h

@@ -131,7 +131,9 @@ enum class MeshIndexType: UnsignedInt {
      * Unsigned byte
      *
      * Corresponds to @ref GL::MeshIndexType::UnsignedByte. Not available on
-     * Vulkan.
+     * Vulkan. While available on OpenGL, at least AMD GPUs are known to
+     * suggest (via debug output) using 16-byte types instead for better
+     * efficiency.
      */
     UnsignedByte,