X-Git-Url: https://git.gag.com/?a=blobdiff_plain;ds=sidebyside;f=debian%2Fpatches%2Ffix-typo;fp=debian%2Fpatches%2Ffix-typo;h=1363e2e2841002cfdfee58e17a084d6bd2ab72e1;hb=fd87e7dcf55c02f2cb5146cf510e637982184823;hp=0000000000000000000000000000000000000000;hpb=8b907c17af32537a21a00e05b20e1379fd61f099;p=fw%2Faltos

diff --git a/debian/patches/fix-typo b/debian/patches/fix-typo
new file mode 100644
index 00000000..1363e2e2
--- /dev/null
+++ b/debian/patches/fix-typo
@@ -0,0 +1,13 @@
+diff --git a/doc/pyro-examples.inc b/doc/pyro-examples.inc
+index 051f0054..1a27a768 100644
+--- a/doc/pyro-examples.inc
++++ b/doc/pyro-examples.inc
+@@ -30,7 +30,7 @@
+ 		the previous stage has completed providing acceleration, to
+ 		minimize drag of the sustainer's coast phase before ignition.
+ 		Recovery, whether the remainder of the flight is nominal or
+-		not, usually works best when the states are separated.  So,
++		not, usually works best when the stages are separated.  So,
+ 		the "best" way to configure a pyro channel for a separation
+ 		charge is to just set "after motor number".  For a 2-stage
+ 		project, set this to "1".  This will cause the pyro channel