summaryrefslogtreecommitdiffstats
path: root/libvirt-qemu-override.c
diff options
context:
space:
mode:
authorEric Blake <eblake@redhat.com>2013-04-19 14:18:14 -0600
committerEric Blake <eblake@redhat.com>2013-04-19 14:31:16 -0600
commitf2b1504a79736cdc17d68581434ca327303f2474 (patch)
treea8061ba6b110be155c532b93bd38ab4c8c0a7aee /libvirt-qemu-override.c
parent919889aa59f93176e46b00956d2dc0693f1f05c1 (diff)
downloadlibvirt-python-split-1.0.5.tar.gz
libvirt-python-split-1.0.5.tar.xz
libvirt-python-split-1.0.5.zip
docs: fix usage of 'onto'v1.0.5-rc1v1.0.5
http://www.uhv.edu/ac/newsletters/writing/grammartip2009.07.01.htm (and several other sites) give hints that 'onto' is best used if you can also add 'up' just before it and still make sense. In many cases in the code base, we really want the two-word form, or even a simplification to just 'on' or 'to'. * docs/hacking.html.in: Use correct 'on to'. * python/libvirt-override.c: Likewise. * src/lxc/lxc_controller.c: Likewise. * src/util/virpci.c: Likewise. * daemon/THREADS.txt: Use simpler 'on'. * docs/formatdomain.html.in: Better usage. * docs/internals/rpc.html.in: Likewise. * src/conf/domain_event.c: Likewise. * src/rpc/virnetclient.c: Likewise. * tests/qemumonitortestutils.c: Likewise. * HACKING: Regenerate. Signed-off-by: Eric Blake <eblake@redhat.com>
Diffstat (limited to 'libvirt-qemu-override.c')
0 files changed, 0 insertions, 0 deletions