Fix typos, make it live

This commit is contained in:
Michael Snoyman 2018-01-03 15:57:44 +02:00
parent 5fdd21f3ed
commit ed0dad8d48
No known key found for this signature in database
GPG key ID: A048E8C057E86876
2 changed files with 4 additions and 4 deletions

View file

@ -1,6 +1,6 @@
- file: posts/drop-conduits-finalizers.md - file: posts/drop-conduits-finalizers.md
title: "Drop Conduit's Finalizers?" title: "Drop Conduit's Finalizers?"
time: 2018-01-04T11:00:00Z time: 2018-01-03T13:57:00Z
description: "Time to ask a really hard question: is it time to remove Conduit's finalizer concept from the library?" description: "Time to ask a really hard question: is it time to remove Conduit's finalizer concept from the library?"
- file: posts/review-bridge-program.md - file: posts/review-bridge-program.md
title: Review of The Bridge strength program title: Review of The Bridge strength program

View file

@ -38,13 +38,13 @@ is almost always fine in practice, but clearly not a mathematical law.
relies on using the type paramter on the `Pipe` type to eliminate relies on using the type paramter on the `Pipe` type to eliminate
leftovers, but leftovers are not a topic I'm raising right now. leftovers, but leftovers are not a topic I'm raising right now.
None of this is new information, so why am I writing this blog post None of this is new information; so why am I writing this blog post
now. The first is that I'm already working on a breaking changes to now? The first is that I'm already working on a breaking change to
Conduit to standardize naming and eliminate some legacy type and Conduit to standardize naming and eliminate some legacy type and
operator names. See operator names. See
[the discussion](https://github.com/snoyberg/conduit/issues/283) and [the discussion](https://github.com/snoyberg/conduit/issues/283) and
[initial comparison](https://github.com/snoyberg/conduit/pull/338/files) [initial comparison](https://github.com/snoyberg/conduit/pull/338/files)
for more details. This natural leads me to ask related questions. for more details. This naturally leads me to ask related questions.
More to the point: after having worked with Conduit for years, my More to the point: after having worked with Conduit for years, my
initial concerns about prompt finalization seem to have been initial concerns about prompt finalization seem to have been