diff options
| author | Cœur <coeur@gmx.fr> | 2022-04-25 19:27:18 +0800 |
|---|---|---|
| committer | Leo Izen <leo.izen@gmail.com> | 2022-04-25 09:07:18 -0400 |
| commit | bb5b4b1ba61b67da40c85c34376aced9383fc366 (patch) | |
| tree | b917b0ad45f31c1187c47424de4159cc28aa730f /DOCS | |
| parent | 6407095871b8f177996a6ec3ee9a8c4f06bd63ee (diff) | |
| download | mpv-bb5b4b1ba61b67da40c85c34376aced9383fc366.tar.bz2 mpv-bb5b4b1ba61b67da40c85c34376aced9383fc366.tar.xz | |
various: fix typos
Diffstat (limited to 'DOCS')
| -rw-r--r-- | DOCS/man/options.rst | 2 | ||||
| -rw-r--r-- | DOCS/man/vo.rst | 2 | ||||
| -rw-r--r-- | DOCS/tech-overview.txt | 4 |
3 files changed, 4 insertions, 4 deletions
diff --git a/DOCS/man/options.rst b/DOCS/man/options.rst index f2cf228282..5d3cdecd32 100644 --- a/DOCS/man/options.rst +++ b/DOCS/man/options.rst @@ -1198,7 +1198,7 @@ Video When testing, you should start by using ``hwdec=auto-safe`` as it will limit itself to choosing from hwdecs that are actively supported by the - development team. If that doesn't result in working hardare decoding, + development team. If that doesn't result in working hardware decoding, you can try ``hwdec=auto`` to have it attempt to load every possible hwdec, but if ``auto-safe`` didn't work, you will probably need to know exactly which hwdec matches your hardware and read up on that entry diff --git a/DOCS/man/vo.rst b/DOCS/man/vo.rst index 290cc3ad96..e453fdcca1 100644 --- a/DOCS/man/vo.rst +++ b/DOCS/man/vo.rst @@ -648,7 +648,7 @@ Available video output drivers are: (default: display resolution) ``--drm-vrr-enabled=<no|yes|auto>`` - Toggle use of Variable Refresh Rate (VRR), aka Freesync or Adapative Sync + Toggle use of Variable Refresh Rate (VRR), aka Freesync or Adaptive Sync on compatible systems. VRR allows for the display to be refreshed at any rate within a range (usually ~40Hz-60Hz for 60Hz displays). This can help with playback of 24/25/50fps content. Support depends on the use of a diff --git a/DOCS/tech-overview.txt b/DOCS/tech-overview.txt index 4bb06ff764..dd21322bbb 100644 --- a/DOCS/tech-overview.txt +++ b/DOCS/tech-overview.txt @@ -377,7 +377,7 @@ without causing conflicts with other library users in the same process. To any piece of code, a "safe" library's API can simply be used, without having to worry about other API users that may be around somewhere. -Libraries are often not library safe, because they they use global mutable state +Libraries are often not library safe, because they use global mutable state or other "global" resources. Typical examples include use of signals, simple global variables (like hsearch() in libc), or internal caches not protected by locks. @@ -481,7 +481,7 @@ VOs, AOs, demuxers, and more. The frontend usually calls "down" the usage hierarchy: mpctx almost on top, then things like vo/ao, and utility code on the very bottom. -"Callback hell" is when when components call both up and down the hierarchy, +"Callback hell" is when components call both up and down the hierarchy, which for example leads to accidentally recursion, reentrancy problems, or locking nightmares. This is avoided by (mostly) calling only down the hierarchy. Basically the call graph forms a DAG. The other direction is handled by event |