X-Git-Url: https://git.cworth.org/git?a=blobdiff_plain;f=src%2Fcairo%2Fa_chain_of_bugs.mdwn;fp=src%2Fcairo%2Fa_chain_of_bugs.mdwn;h=10dd2875866e8865975273f9587497f5aa1278ab;hb=2584359a20dd9d8766571dd5a50a0b739767dd4a;hp=a944ddd64a14023aeb77143938eb930618b91af5;hpb=adffeae8812a84f105e4c280ea873c2bdd415c3d;p=cworth.org

diff --git a/src/cairo/a_chain_of_bugs.mdwn b/src/cairo/a_chain_of_bugs.mdwn
index a944ddd..10dd287 100644
--- a/src/cairo/a_chain_of_bugs.mdwn
+++ b/src/cairo/a_chain_of_bugs.mdwn
@@ -52,9 +52,9 @@ rendering models.
 To explain a bit, (but ignoring many gory details), a PDF knockout
 group can be a very complicated thing, so poppler has some fairly
 sophisticated code to handle these. This support involves rendering
-everything in the group twice and then using cairo's DEST_OUT and ADD
+everything in the group twice and then using cairo's `DEST_OUT` and `ADD`
 compositing operators to properly combine them. Well, PostScript can't
-do fancy compositing like DEST_OUT and ADD, so of course cairo falls
+do fancy compositing like `DEST_OUT` and `ADD`, so of course cairo falls
 back to image-based rendering for things. The irony here is that the
 only reason cairo is using a knockout group in the original PDF file
 is to _prevent_ any compositing from happening, (the fallback image