summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFelix Gruber2015-10-18 17:11:50 +0200
committerJoey Hess2015-10-18 14:14:30 -0400
commitf125146f76a14caf361d031b6aae04b551b95194 (patch)
treee4f0fca74e3d38d60483c5727775cf2cb73b773c
parent6c96481dd39d1e0fbcef8dd68300a66e13db9ed9 (diff)
fix typo: propigate → propagate
-rw-r--r--doc/forum/chroot_for_sbuild/comment_5_dec82cad1490a22c3f2fbbaa4edbd9f0._comment2
-rw-r--r--doc/todo/info_propigation_out_of_nested_properties.mdwn8
2 files changed, 5 insertions, 5 deletions
diff --git a/doc/forum/chroot_for_sbuild/comment_5_dec82cad1490a22c3f2fbbaa4edbd9f0._comment b/doc/forum/chroot_for_sbuild/comment_5_dec82cad1490a22c3f2fbbaa4edbd9f0._comment
index f1bc6717..48fb38e6 100644
--- a/doc/forum/chroot_for_sbuild/comment_5_dec82cad1490a22c3f2fbbaa4edbd9f0._comment
+++ b/doc/forum/chroot_for_sbuild/comment_5_dec82cad1490a22c3f2fbbaa4edbd9f0._comment
@@ -26,7 +26,7 @@ should be taken when using `ignoreInfo`.
It *might* be ok to ignoreInfo in this case; the agument would go that this
is a chroot being used to create a sbuild image, so any Info belonging to
properties of the chroot doesn't affect the host that it's built on,
-and so it doesn't need to propigate out. But, consider that this would
+and so it doesn't need to propagate out. But, consider that this would
break any properties inside the chroot that use privdata, since
privdata works via info.
diff --git a/doc/todo/info_propigation_out_of_nested_properties.mdwn b/doc/todo/info_propigation_out_of_nested_properties.mdwn
index 536d6719..4176213a 100644
--- a/doc/todo/info_propigation_out_of_nested_properties.mdwn
+++ b/doc/todo/info_propigation_out_of_nested_properties.mdwn
@@ -1,6 +1,6 @@
> Now [[fixed|done]]!! --[[Joey]]
-Currently, Info about a Host's Properties is propigated to the host by
+Currently, Info about a Host's Properties is propagated to the host by
examining the tree of Properties.
This works, but there's one problem. Consider this example:
@@ -9,8 +9,8 @@ This works, but there's one problem. Consider this example:
(Just (System (Debian Unstable) _)) -> ensureProperty foo
_ -> ensureProperty bar
-Here, the Info of `foo` is not propigated out. Nor is `bar`'s Info.
-It's not really clear if just one Info, or both should be propigated out.
+Here, the Info of `foo` is not propagated out. Nor is `bar`'s Info.
+It's not really clear if just one Info, or both should be propagated out.
----
@@ -50,7 +50,7 @@ Here withInfoFrom adds foo and bar as child properties of the demo property
that (may) call them.
This approach is not fully type safe; it would be possible to call
-withInfoFrom in a way that didn't let it propigate the info.
+withInfoFrom in a way that didn't let it propagate the info.
And again this doesn't solve the problem that IO can be needed to get
a parameter of a child property.