demo

diff --git a/Makefile b/Makefile
index 9410c30cd7593e3316c00d40ddc02f3eb8b5494d..e69c4f79904ab3b18175f66e567ca05a21eee021 100644 (file)
--- a/Makefile
+++ b/Makefile
@@ -1,5 +1,5 @@
 
-SLIDES=archive-vcs manpage libavg access-table
+SLIDES=archive-vcs manpage demo-placeholder libavg access-table
 
 SLIDEFILES=$(addsuffix .ps, $(SLIDES))
 

diff --git a/demo-placeholder.fig b/demo-placeholder.fig
new file mode 100644 (file)
index 0000000..4b54f2a
--- /dev/null
+++ b/demo-placeholder.fig
@@ -0,0 +1,10 @@
+#FIG 3.2  Produced by xfig version 3.2.5b
+Landscape
+Center
+Metric
+A4      
+100.00
+Single
+-2
+1200 2
+4 0 0 50 -1 0 24 0.0000 4 345 1185 2745 4500 (demo)\001

diff --git a/talk.txt b/talk.txt
index 4140e3ec1918b08e030089f9e90d9893e46d70f2..8f3ccb56f1445a0c2a64db23c01ba6ca570e0e3e 100644 (file)
--- a/talk.txt
+++ b/talk.txt
@@ -37,12 +37,12 @@ whether the maintainer uses dgit, other git tools, quilt, CVS or SCCS.
 With dgit you do all direct source code management in git.  As a dgit
 user you do not interact with the archive directly.
 
+[demo]
+
 dgit is particularly useful for NMUers: you can prepare an RC bugfix,
-with full support from git, withut needing to know anything about the
+with full support from git, without needing to know anything about the
 package's usual VCS arrangements.
 
-[demo]
-
 dgit also has great potential for downstreams - that is, derivatives
 and users who want to modify a package.  Having used dgit clone or
 fetch, you can merge into your downstream branch.  (There are some