aboutsummaryrefslogtreecommitdiff
path: root/haddock-api
diff options
context:
space:
mode:
authorYuchen Pei <hi@ypei.me>2022-07-19 11:17:13 +1000
committerYuchen Pei <hi@ypei.me>2022-07-19 11:17:13 +1000
commitd2fbd46cb3dcbdea0d981e74f6a2b9b793e93c38 (patch)
tree9d1504d516376db24180ca1b86aec6364639fbca /haddock-api
parent702977b075dfdfc12275c30d3b395b1f811f640e (diff)
typo
Diffstat (limited to 'haddock-api')
-rw-r--r--haddock-api/README.org2
1 files changed, 1 insertions, 1 deletions
diff --git a/haddock-api/README.org b/haddock-api/README.org
index 298d2306..606a8c5f 100644
--- a/haddock-api/README.org
+++ b/haddock-api/README.org
@@ -121,7 +121,7 @@ or one big org file containing all packages? Currently haddorg-api
takes the latter approach. It produces one org file per package, but
cross-package links are generated in a way so that they only work in
one big org file from concatenation of separate package org
-files. This may become unwieldy, especially when a big org file
+files. This may become unwieldy, especially when the big org file
contains large libraries like base and ghc. For links to work in the
alternative approach, the links have to be aware of org files of other
packages.