Some typo fixes.

[nageru-docs] / video.rst

diff --git a/video.rst b/video.rst
index 1244b0944b6b0a39c040a17520169f5634477310..c418e92a39e12b4fd24ece509dd0166e082baaca 100644 (file)
--- a/video.rst
+++ b/video.rst
@@ -123,7 +123,7 @@ hole)::
 
 or by setting it up on-the-fly through ACMP::
 
-  add 1 stream unix:///home/user/caspar.sock -vf format=pix_fmts=bgra -f nut -listen 1
+  add 1 stream unix:///home/user/caspar.sock -c:v rawvideo -vf format=pix_fmts=bgra -f nut -listen 1
 
 You can then use *unix:///home/user/caspar.sock* as a video input to Nageru on the
 same machine, and then use e.g. *OverlayEffect* to overlay it on your video chains.
@@ -143,7 +143,7 @@ streams are one-shot, and so are FFmpeg's UNIX domain sockets.* This means that,
 in practice, if Nageru ever disconnects from CasparCG for any reason, the socket
 is “used up”, and you will need to recreate it somehow (e.g., by restarting CasparCG).
 Also note that the old socket still lingers in place even after being useless,
-so you will _first_ need to remove it, and CasparCG does not do this for you.
+so you will *first* need to remove it, and CasparCG does not do this for you.
 The simplest way to deal with this is probably to have a wrapper script of some
 sort that orchestrates Nageru, CasparCG and your client for you, so that everything
 is taken up and down in the right order; it may be cumbersome and require some
@@ -159,7 +159,7 @@ between the two.
 
 In general, the integration between Nageru and CasparCG leaves a bit to be
 desired, and in general, the combination of CasparCG + Nageru will require
-a beefire machine than Nageru alone. However, it also provides a much richer
+a beefier machine than Nageru alone. However, it also provides a much richer
 environment for graphics, so for many use cases, it will be worth it.
 
 .. [#rawvideo] Good video codecs that support alpha are rare, so as long as CasparCG