diff options
| author | Stefan Weil <sw@weilnetz.de> | 2015-10-09 17:13:35 +0200 |
|---|---|---|
| committer | Stefan Weil <sw@weilnetz.de> | 2015-10-09 17:13:35 +0200 |
| commit | 9c7efb7633ba62cd80c93e83284663f805bb3031 (patch) | |
| tree | a462dc1715366e72e74e45dcc24f4d3a1c241772 /examples | |
| parent | 97f442ef2aa65ade6bea11e90054c57b90abbaca (diff) | |
| download | libtdevnc-9c7efb7633ba62cd80c93e83284663f805bb3031.tar.gz libtdevnc-9c7efb7633ba62cd80c93e83284663f805bb3031.zip | |
Fix some typos (found by codespell)
Signed-off-by: Stefan Weil <sw@weilnetz.de>
Diffstat (limited to 'examples')
| -rw-r--r-- | examples/camera.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/examples/camera.c b/examples/camera.c index 58ab1c3..2e54da7 100644 --- a/examples/camera.c +++ b/examples/camera.c @@ -16,7 +16,7 @@ * Christian Daschill * * - * Answer: Originally, I thought about using seperate threads and using a + * Answer: Originally, I thought about using separate threads and using a * mutex to determine when the frame buffer was being accessed by any client * so we could determine a safe time to take a picture. The probem is, we * are lock-stepping everything with framebuffer access. Why not be a @@ -31,7 +31,7 @@ * as the libvncserver should not stall on transmitting to any single * client. * - * Another solution would be to provide a seperate framebuffer for each + * Another solution would be to provide a separate framebuffer for each * client and use mutexes to determine if any particular client is ready for * a snapshot. This way, your not updating a framebuffer for a slow client * while it is being transferred. |