/dev/dri/card0 -> /dev/drm0

2 files changed, 7 insertions, 7 deletions

diff --git a/lib/libdrm/man/drm.7 b/lib/libdrm/man/drm.7
index bbd3b40ef..bd7769918 100644
--- a/lib/libdrm/man/drm.7
+++ b/lib/libdrm/man/drm.7
@@ -34,7 +34,7 @@ simplify the API.
 When a GPU is detected, the DRM system loads a driver for the detected
 hardware type. Each connected GPU is then presented to user-space via
 a character-device that is usually available as
-.Pa /dev/dri/card0
+.Pa /dev/drm0
 and can be accessed with
 .Xr open 2
 and
diff --git a/lib/libdrm/man/drm.xml b/lib/libdrm/man/drm.xml
index 5a49fe13e..c890d5be9 100644
--- a/lib/libdrm/man/drm.xml
+++ b/lib/libdrm/man/drm.xml
@@ -49,8 +49,8 @@
           applications.</para>
 
     <para>In earlier days, the kernel framework was solely used to provide raw
-          hardware access to priviledged user-space processes which implement
-          all the hardware abstraction layers. But more and more tasks where
+          hardware access to privileged user-space processes which implement
+          all the hardware abstraction layers. But more and more tasks were
           moved into the kernel. All these interfaces are based on
           <citerefentry><refentrytitle>ioctl</refentrytitle><manvolnum>2</manvolnum></citerefentry>
           commands on the DRM character device. The <emphasis>libdrm</emphasis>
@@ -60,11 +60,11 @@
     <para>When a GPU is detected, the DRM system loads a driver for the detected
           hardware type. Each connected GPU is then presented to user-space via
           a character-device that is usually available as
-          <filename>/dev/dri/card0</filename> and can be accessed with
+          <filename>/dev/drm0</filename> and can be accessed with
           <citerefentry><refentrytitle>open</refentrytitle><manvolnum>2</manvolnum></citerefentry>
           and
           <citerefentry><refentrytitle>close</refentrytitle><manvolnum>2</manvolnum></citerefentry>.
-          However, it still depends on the grapics driver which interfaces are
+          However, it still depends on the graphics driver which interfaces are
           available on these devices. If an interface is not available, the
           syscalls will fail with <literal>EINVAL</literal>.</para>
 
@@ -119,8 +119,8 @@
   <refsect1>
     <title>Reporting Bugs</title>
     <para>Bugs in this manual should be reported to
-          http://bugs.freedesktop.org under the "Mesa" product, with "Other" or
-          "libdrm" as the component.</para>
+      https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&amp;component=libdrm
+      under the "DRI" product, component "libdrm"</para>
   </refsect1>
 
   <refsect1>