diff options
| author | Daniel Borca <dborca@users.sourceforge.net> | 2004-02-20 09:47:42 +0000 |
|---|---|---|
| committer | Daniel Borca <dborca@users.sourceforge.net> | 2004-02-20 09:47:42 +0000 |
| commit | 2aa84490c02bc304f31198c6f3d44a31093e664b (patch) | |
| tree | effaea72ce8c07ba080a7d590f5b4c7a0c034ea6 /docs/README.DJ | |
| parent | 304d3aa9cb727eb4cd4797c33f8e13e5ac4285a9 (diff) | |
fixed some typos
Diffstat (limited to 'docs/README.DJ')
| -rw-r--r-- | docs/README.DJ | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/README.DJ b/docs/README.DJ index 2e663d2ee7..63d3711e0e 100644 --- a/docs/README.DJ +++ b/docs/README.DJ @@ -128,8 +128,8 @@ FAQ: Q) What is NUL driver good for, if I don't get any output at all? A) For debugging. The NUL driver is very much like OSMesa. Everything is - done just the same as VESA/VGA drivers, only it doesn't touches your - video hardware. You can query the actual buffer by issuing: + done just the same as VESA/VGA drivers, only it doesn't touch your video + hardware. You can query the actual buffer by issuing: DMesaGetIntegerv(DMESA_GET_BUFFER_ADDR, &buffer); and dump it to a file. |