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-21 13:01:51 +1000
commit2e633babce6849987114c1ecc3ec2be8f14a0e4b (patch)
tree094852f52fa5672caec147ed1b4efb952197cd03 /haddock-api
parent6955f36651c5aad90475398480450974fcb276bd (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.