;doc: journal: separate periodic rules' two meanings

Shake.hs

@@ -376,7 +376,7 @@ main = do
         deps <- liftIO $ filter (/= src) . filter (".m4.md" `isSuffixOf`) . map (dir </>) <$> S.getDirectoryContents dir
         need $ [src, commonm4, packagem4, tmpl] ++ deps
         when (dir=="hledger") $ need commandmds
-        cmd_ Shell sed "-i -e" ("'s/(_monthyear_}}, *)\\{\\{[^}]+/\\1{{"++mandate++"/;'") packagem4
+        cmd_ Shell sed "-i -e" ("'s/(_monthyear_}}, *)\\{\\{[^}]+/\\1{{"++mandate++"/;'") packagem4  -- XXX forces a rebuild every time
         cmd Shell
           "m4 -P -DMAN -I" dir commonm4 packagem4 src "|"
           pandoc fromsrcmd "-s" "--template" tmpl

hledger-lib/hledger_journal.m4.md

@@ -1436,7 +1436,6 @@ Periodic transaction rules describe transactions that recur.
 They allow hledger to generate temporary future transactions to help with forecasting,
 so you don't have to write out each one in the journal,
 and it's easy to try out different forecasts.
-Secondly, they are also used to define the budgets shown in budget reports.
 
 Periodic transactions can be a little tricky, so before you use them,
 read this whole section - or at least these tips:
@@ -1454,6 +1453,10 @@ read this whole section - or at least these tips:
    `~ every 10th day of month from 2020/01`, which is equivalent to <br>
    `~ every 10th day of month from 2020/01/01`, will be adjusted to start on 2019/12/10.
 
+Periodic transaction rules also have a second meaning:
+they are used to define budget goals, shown in [budget reports](hledger.html#budget-report).
+
+
 ### Periodic rule syntax
 
 A periodic transaction rule looks like a normal journal entry,