diff --git a/manual.html b/manual.html
index ac2f8ab..f527ee9 100644
--- a/manual.html
+++ b/manual.html
@@ -24,7 +24,6 @@ General Public License for more details.
 <meta name="Generator" content="makeinfo">
 <link href="#Top" rel="start" title="Top">
 <link href="#Keystroke-Index" rel="index" title="Keystroke Index">
-<link href="#SEC_Contents" rel="contents" title="Table of Contents">
 <link href="dir.html#Top" rel="up" title="(dir)">
 <style type="text/css">
 <!--
@@ -64,113 +63,10 @@ ul.no-bullet {list-style: none}
 
 
 
-<a name="SEC_Contents"></a>
-<h2 class="contents-heading">Table of Contents</h2>
-
-<div class="contents">
-
-<ul class="no-bullet">
-  <li><a name="toc-Introduction-1" href="#Introduction">1 Introduction</a></li>
-  <li><a name="toc-Target-Audience-1" href="#Target-Audience">2 Target Audience</a></li>
-  <li><a name="toc-A-Brief-Introduction-to-the-Zettelkasten-Method-1" href="#A-Brief-Introduction-to-the-Zettelkasten-Method">3 A Brief Introduction to the Zettelkasten Method</a>
-  <ul class="no-bullet">
-    <li><a name="toc-Fleeting-notes-1" href="#Fleeting-notes">3.1 Fleeting notes</a></li>
-    <li><a name="toc-Permanent-notes-1" href="#Permanent-notes">3.2 Permanent notes</a></li>
-  </ul></li>
-  <li><a name="toc-Installation-1" href="#Installation">4 Installation</a>
-  <ul class="no-bullet">
-    <li><a name="toc-Installing-from-MELPA-1" href="#Installing-from-MELPA">4.1 Installing from MELPA</a></li>
-    <li><a name="toc-Installing-from-Apt-1" href="#Installing-from-Apt">4.2 Installing from Apt</a></li>
-    <li><a name="toc-Installing-from-the-Git-Repository-1" href="#Installing-from-the-Git-Repository">4.3 Installing from the Git Repository</a></li>
-    <li><a name="toc-Post_002dInstallation-Tasks-1" href="#Post_002dInstallation-Tasks">4.4 Post-Installation Tasks</a></li>
-  </ul></li>
-  <li><a name="toc-Getting-Started-1" href="#Getting-Started">5 Getting Started</a></li>
-  <li><a name="toc-Anatomy-of-an-Org_002droam-File-1" href="#Anatomy-of-an-Org_002droam-File">6 Anatomy of an Org-roam File</a>
-  <ul class="no-bullet">
-    <li><a name="toc-Titles-1" href="#Titles">6.1 Titles</a></li>
-    <li><a name="toc-Tags-1" href="#Tags">6.2 Tags</a></li>
-    <li><a name="toc-File-Refs-1" href="#File-Refs">6.3 File Refs</a></li>
-  </ul></li>
-  <li><a name="toc-The-Templating-System-1" href="#The-Templating-System">7 The Templating System</a>
-  <ul class="no-bullet">
-    <li><a name="toc-Template-Walkthrough-1" href="#Template-Walkthrough">7.1 Template Walkthrough</a></li>
-    <li><a name="toc-Org_002droam-Template-Expansion-1" href="#Org_002droam-Template-Expansion">7.2 Org-roam Template Expansion</a></li>
-  </ul></li>
-  <li><a name="toc-Concepts-and-Configuration-1" href="#Concepts-and-Configuration">8 Concepts and Configuration</a>
-  <ul class="no-bullet">
-    <li><a name="toc-Directories-and-Files-1" href="#Directories-and-Files">8.1 Directories and Files</a></li>
-    <li><a name="toc-The-Org_002droam-Buffer-1" href="#The-Org_002droam-Buffer">8.2 The Org-roam Buffer</a></li>
-    <li><a name="toc-Org_002droam-Files-1" href="#Org_002droam-Files">8.3 Org-roam Files</a></li>
-    <li><a name="toc-Org_002droam-Faces-1" href="#Org_002droam-Faces">8.4 Org-roam Faces</a></li>
-  </ul></li>
-  <li><a name="toc-Inserting-Links-1" href="#Inserting-Links">9 Inserting Links</a></li>
-  <li><a name="toc-Navigating-Around-1" href="#Navigating-Around">10 Navigating Around</a>
-  <ul class="no-bullet">
-    <li><a name="toc-Index-File-1" href="#Index-File">10.1 Index File</a></li>
-  </ul></li>
-  <li><a name="toc-Encryption-1" href="#Encryption">11 Encryption</a></li>
-  <li><a name="toc-Graphing-1" href="#Graphing">12 Graphing</a>
-  <ul class="no-bullet">
-    <li><a name="toc-Graph-Options-1" href="#Graph-Options">12.1 Graph Options</a></li>
-    <li><a name="toc-Excluding-Nodes-and-Edges-1" href="#Excluding-Nodes-and-Edges">12.2 Excluding Nodes and Edges</a></li>
-  </ul></li>
-  <li><a name="toc-Org_002droam-Completion-System-1" href="#Org_002droam-Completion-System">13 Org-roam Completion System</a></li>
-  <li><a name="toc-Roam-Protocol-1" href="#Roam-Protocol">14 Roam Protocol</a>
-  <ul class="no-bullet">
-    <li><a name="toc-Installation-2" href="#Installation-_00281_0029">14.1 Installation</a></li>
-    <li><a name="toc-The-roam_002dfile-protocol-1" href="#The-roam_002dfile-protocol">14.2 The roam-file protocol</a></li>
-    <li><a name="toc-The-roam_002dref-protocol-1" href="#The-roam_002dref-protocol">14.3 The roam-ref protocol</a></li>
-  </ul></li>
-  <li><a name="toc-Daily_002dnotes-1" href="#Daily_002dnotes">15 Daily-notes</a>
-  <ul class="no-bullet">
-    <li><a name="toc-Configuration-1" href="#Configuration">15.1 Configuration</a></li>
-    <li><a name="toc-Capturing-and-finding-daily_002dnotes-1" href="#Capturing-and-finding-daily_002dnotes">15.2 Capturing and finding daily-notes</a></li>
-    <li><a name="toc-Navigation-1" href="#Navigation">15.3 Navigation</a></li>
-  </ul></li>
-  <li><a name="toc-Diagnosing-and-Repairing-Files-1" href="#Diagnosing-and-Repairing-Files">16 Diagnosing and Repairing Files</a></li>
-  <li><a name="toc-Finding-Unlinked-References-1" href="#Finding-Unlinked-References">17 Finding Unlinked References</a></li>
-  <li><a name="toc-Performance-Optimization-1" href="#Performance-Optimization">18 Performance Optimization</a>
-  <ul class="no-bullet">
-    <li><a name="toc-TODO-Profiling-Key-Operations" href="#Profiling-Key-Operations">18.1 <strong>TODO</strong> Profiling Key Operations</a></li>
-    <li><a name="toc-Garbage-Collection-1" href="#Garbage-Collection">18.2 Garbage Collection</a></li>
-  </ul></li>
-  <li><a name="toc-Appendix-1" href="#Appendix">19 Appendix</a>
-  <ul class="no-bullet">
-    <li><a name="toc-Note_002dtaking-Workflows-1" href="#Note_002dtaking-Workflows">19.1 Note-taking Workflows</a></li>
-    <li><a name="toc-Ecosystem-1" href="#Ecosystem">19.2 Ecosystem</a>
-    <ul class="no-bullet">
-      <li><a name="toc-Browsing-History-with-winner_002dmode-1" href="#Browsing-History-with-winner_002dmode">19.2.1 Browsing History with winner-mode</a></li>
-      <li><a name="toc-Versioning-Notes-1" href="#Versioning-Notes">19.2.2 Versioning Notes</a></li>
-      <li><a name="toc-Full_002dtext-search-interface-with-Deft-1" href="#Full_002dtext-search-interface-with-Deft">19.2.3 Full-text search interface with Deft</a></li>
-      <li><a name="toc-Org_002djournal-1" href="#Org_002djournal">19.2.4 Org-journal</a></li>
-      <li><a name="toc-Note_002dtaking-Add_002dons-1" href="#Note_002dtaking-Add_002dons">19.2.5 Note-taking Add-ons</a>
-      <ul class="no-bullet">
-        <li><a name="toc-Org_002ddownload-1" href="#Org_002ddownload">Org-download</a></li>
-        <li><a name="toc-mathpix_002eel" href="#mathpixel">mathpix.el</a></li>
-        <li><a name="toc-Org_002dnoter-_002f-Interleave-1" href="#Org_002dnoter-_002f-Interleave">Org-noter / Interleave</a></li>
-        <li><a name="toc-Bibliography-1" href="#Bibliography">Bibliography</a></li>
-        <li><a name="toc-Spaced-Repetition-1" href="#Spaced-Repetition">Spaced Repetition</a></li>
-      </ul></li>
-    </ul></li>
-  </ul></li>
-  <li><a name="toc-FAQ-1" href="#FAQ">20 FAQ</a>
-  <ul class="no-bullet">
-    <li><a name="toc-How-do-I-have-more-than-one-Org_002droam-directory_003f-1" href="#How-do-I-have-more-than-one-Org_002droam-directory_003f">20.1 How do I have more than one Org-roam directory?</a></li>
-    <li><a name="toc-How-do-I-migrate-from-Roam-Research_003f-1" href="#How-do-I-migrate-from-Roam-Research_003f">20.2 How do I migrate from Roam Research?</a></li>
-    <li><a name="toc-How-do-I-create-a-note-whose-title-already-matches-one-of-the-candidates_003f-1" href="#How-do-I-create-a-note-whose-title-already-matches-one-of-the-candidates_003f">20.3 How do I create a note whose title already matches one of the candidates?</a></li>
-  </ul></li>
-  <li><a name="toc-Keystroke-Index-1" href="#Keystroke-Index">Appendix A Keystroke Index</a></li>
-  <li><a name="toc-Command-Index-1" href="#Command-Index">Appendix B Command Index</a></li>
-  <li><a name="toc-Function-Index-1" href="#Function-Index">Appendix C Function Index</a></li>
-  <li><a name="toc-Variable-Index-1" href="#Variable-Index">Appendix D Variable Index</a></li>
-</ul>
-</div>
-
-
 <a name="Top"></a>
 <div class="header">
 <p>
-Next: <a href="#Introduction" accesskey="n" rel="next">Introduction</a>, Up: <a href="dir.html#Top" accesskey="u" rel="up">(dir)</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Introduction" accesskey="n" rel="next">Introduction</a>, Up: <a href="dir.html#Top" accesskey="u" rel="up">(dir)</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Org_002droam-User-Manual"></a>
 <h1 class="top">Org-roam User Manual</h1>
@@ -359,6 +255,19 @@ Ecosystem
 </td></tr>
 <tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
 
+Note-taking Add-ons
+
+</pre></th></tr><tr><td align="left" valign="top">&bull; <a href="#Org_002ddownload">Org-download</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#mathpixel">mathpix.el</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Org_002dnoter-_002f-Interleave">Org-noter / Interleave</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Bibliography">Bibliography</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
+</td></tr>
+<tr><td align="left" valign="top">&bull; <a href="#Spaced-Repetition">Spaced Repetition</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
+</td></tr>
+<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
 
 FAQ
 
@@ -376,7 +285,7 @@ FAQ
 <a name="Introduction"></a>
 <div class="header">
 <p>
-Next: <a href="#Target-Audience" accesskey="n" rel="next">Target Audience</a>, Previous: <a href="#Top" accesskey="p" rel="prev">Top</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Target-Audience" accesskey="n" rel="next">Target Audience</a>, Previous: <a href="#Top" accesskey="p" rel="prev">Top</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Introduction-1"></a>
 <h2 class="chapter">1 Introduction</h2>
@@ -399,22 +308,34 @@ to further introduce features enabled by the Emacs ecosystem.
 <p>Org-roam provides several benefits over other tooling:
 </p>
 <ul>
-<li> Privacy and SecurityEdit your personal wiki completely offline, entirely in your control. Encrypt your notes with GPG.
+<li> Privacy and SecurityEdit your personal wiki completely offline, entirely
+in your control. Encrypt your notes with GPG.
 
-</li><li> Longevity of Plain TextUnlike web solutions like Roam research, the notes are first and foremost plain Org-mode files &ndash; Org-roam simply builds up an auxilliary database to give the personal wiki superpowers. Having your notes in plain-text is crucial for the longevity of your wiki. Never have to worry about proprietary web solutions being taken down. Edit your plain-text notes in notepad if all other editors cease to exist
+</li><li> Longevity of Plain TextUnlike web solutions like Roam research, the notes
+are first and foremost plain Org-mode files &ndash; Org-roam simply builds up an
+auxilliary database to give the personal wiki superpowers. Having your notes
+in plain-text is crucial for the longevity of your wiki. Never have to worry
+about proprietary web solutions being taken down. Edit your plain-text notes
+in notepad if all other editors cease to exist
 
-</li><li> Free and Open SourceOrg-roam is free and open-source, which means that if you feel unhappy with any part of Org-roam, you may choose to extend Org-roam, or open a PR.
+</li><li> Free and Open SourceOrg-roam is free and open-source, which means that if
+you feel unhappy with any part of Org-roam, you may choose to extend Org-roam,
+or open a PR.
 
-</li><li> Leverages the Org-mode ecosystemOver the years, Emacs and Org-mode has developed into a mature system for plain-text organization. Building upon Org-mode already puts Org-roam light-years ahead of many other solutions.
+</li><li> Leverages the Org-mode ecosystemOver the years, Emacs and Org-mode has
+developed into a mature system for plain-text organization. Building upon
+Org-mode already puts Org-roam light-years ahead of many other solutions.
 
-</li><li> Built on EmacsEmacs is also a fantastic interface for editing text, and we can inherit many of the powerful text-navigation and editing packages available to Emacs.
+</li><li> Built on EmacsEmacs is also a fantastic interface for editing text, and we
+can inherit many of the powerful text-navigation and editing packages
+available to Emacs.
 </li></ul>
 
 <hr>
 <a name="Target-Audience"></a>
 <div class="header">
 <p>
-Next: <a href="#A-Brief-Introduction-to-the-Zettelkasten-Method" accesskey="n" rel="next">A Brief Introduction to the Zettelkasten Method</a>, Previous: <a href="#Introduction" accesskey="p" rel="prev">Introduction</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#A-Brief-Introduction-to-the-Zettelkasten-Method" accesskey="n" rel="next">A Brief Introduction to the Zettelkasten Method</a>, Previous: <a href="#Introduction" accesskey="p" rel="prev">Introduction</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Target-Audience-1"></a>
 <h2 class="chapter">2 Target Audience</h2>
@@ -454,7 +375,7 @@ Command Line (1998)
 <a name="A-Brief-Introduction-to-the-Zettelkasten-Method"></a>
 <div class="header">
 <p>
-Next: <a href="#Installation" accesskey="n" rel="next">Installation</a>, Previous: <a href="#Target-Audience" accesskey="p" rel="prev">Target Audience</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Installation" accesskey="n" rel="next">Installation</a>, Previous: <a href="#Target-Audience" accesskey="p" rel="prev">Target Audience</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="A-Brief-Introduction-to-the-Zettelkasten-Method-1"></a>
 <h2 class="chapter">3 A Brief Introduction to the Zettelkasten Method</h2>
@@ -499,7 +420,7 @@ links.
 <a name="Fleeting-notes"></a>
 <div class="header">
 <p>
-Next: <a href="#Permanent-notes" accesskey="n" rel="next">Permanent notes</a>, Up: <a href="#A-Brief-Introduction-to-the-Zettelkasten-Method" accesskey="u" rel="up">A Brief Introduction to the Zettelkasten Method</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Permanent-notes" accesskey="n" rel="next">Permanent notes</a>, Up: <a href="#A-Brief-Introduction-to-the-Zettelkasten-Method" accesskey="u" rel="up">A Brief Introduction to the Zettelkasten Method</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Fleeting-notes-1"></a>
 <h3 class="section">3.1 Fleeting notes</h3>
@@ -515,7 +436,7 @@ thoughts, to be processed later into permanent notes.
 <a name="Permanent-notes"></a>
 <div class="header">
 <p>
-Previous: <a href="#Fleeting-notes" accesskey="p" rel="prev">Fleeting notes</a>, Up: <a href="#A-Brief-Introduction-to-the-Zettelkasten-Method" accesskey="u" rel="up">A Brief Introduction to the Zettelkasten Method</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Previous: <a href="#Fleeting-notes" accesskey="p" rel="prev">Fleeting notes</a>, Up: <a href="#A-Brief-Introduction-to-the-Zettelkasten-Method" accesskey="u" rel="up">A Brief Introduction to the Zettelkasten Method</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Permanent-notes-1"></a>
 <h3 class="section">3.2 Permanent notes</h3>
@@ -531,7 +452,7 @@ addition of different templates to facilitate the creation of these notes.
 <a name="Installation"></a>
 <div class="header">
 <p>
-Next: <a href="#Getting-Started" accesskey="n" rel="next">Getting Started</a>, Previous: <a href="#A-Brief-Introduction-to-the-Zettelkasten-Method" accesskey="p" rel="prev">A Brief Introduction to the Zettelkasten Method</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Getting-Started" accesskey="n" rel="next">Getting Started</a>, Previous: <a href="#A-Brief-Introduction-to-the-Zettelkasten-Method" accesskey="p" rel="prev">A Brief Introduction to the Zettelkasten Method</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Installation-1"></a>
 <h2 class="chapter">4 Installation</h2>
@@ -554,7 +475,7 @@ development repository.
 <a name="Installing-from-MELPA"></a>
 <div class="header">
 <p>
-Next: <a href="#Installing-from-Apt" accesskey="n" rel="next">Installing from Apt</a>, Up: <a href="#Installation" accesskey="u" rel="up">Installation</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Installing-from-Apt" accesskey="n" rel="next">Installing from Apt</a>, Up: <a href="#Installation" accesskey="u" rel="up">Installation</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Installing-from-MELPA-1"></a>
 <h3 class="section">4.1 Installing from MELPA</h3>
@@ -611,7 +532,7 @@ using:
 <a name="Installing-from-Apt"></a>
 <div class="header">
 <p>
-Next: <a href="#Installing-from-the-Git-Repository" accesskey="n" rel="next">Installing from the Git Repository</a>, Previous: <a href="#Installing-from-MELPA" accesskey="p" rel="prev">Installing from MELPA</a>, Up: <a href="#Installation" accesskey="u" rel="up">Installation</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Installing-from-the-Git-Repository" accesskey="n" rel="next">Installing from the Git Repository</a>, Previous: <a href="#Installing-from-MELPA" accesskey="p" rel="prev">Installing from MELPA</a>, Up: <a href="#Installation" accesskey="u" rel="up">Installation</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Installing-from-Apt-1"></a>
 <h3 class="section">4.2 Installing from Apt</h3>
@@ -629,14 +550,21 @@ using Apt:
 <a name="Installing-from-the-Git-Repository"></a>
 <div class="header">
 <p>
-Next: <a href="#Post_002dInstallation-Tasks" accesskey="n" rel="next">Post-Installation Tasks</a>, Previous: <a href="#Installing-from-Apt" accesskey="p" rel="prev">Installing from Apt</a>, Up: <a href="#Installation" accesskey="u" rel="up">Installation</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Post_002dInstallation-Tasks" accesskey="n" rel="next">Post-Installation Tasks</a>, Previous: <a href="#Installing-from-Apt" accesskey="p" rel="prev">Installing from Apt</a>, Up: <a href="#Installation" accesskey="u" rel="up">Installation</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Installing-from-the-Git-Repository-1"></a>
 <h3 class="section">4.3 Installing from the Git Repository</h3>
 
-<p>You may install Org-roam directly from the repository on <a href="https://github.com/org-roam/org-roam">GitHub</a> if you like. This will give you access to the latest version hours or days before it appears on MELPA, and months (or more) before it is added to the Debian or Ubuntu repositories. This will also give you access to various developmental branches that may be available. 
+<p>You may install Org-roam directly from the repository on <a href="https://github.com/org-roam/org-roam">GitHub</a> if you like.
+This will give you access to the latest version hours or days before it appears
+on MELPA, and months (or more) before it is added to the Debian or Ubuntu
+repositories. This will also give you access to various developmental branches
+that may be available.
 </p>
-<p>Note, however, that development version, and especially any feature branches, may not always be in working order. You&rsquo;ll need to be prepared to do some debugging, or to manually roll-back to working versions, if you install from GitHub.
+<p>Note, however, that development version, and especially any feature branches,
+may not always be in working order. You&rsquo;ll need to be prepared to do some
+debugging, or to manually roll-back to working versions, if you install from
+GitHub.
 </p>
 <p>Installing from GitHub requires that you clone the repository:
 </p>
@@ -646,14 +574,16 @@ Next: <a href="#Post_002dInstallation-Tasks" accesskey="n" rel="next">Post-Insta
 
 <p>where <code>./path/to/org/roam</code> is the location you will store your copy of the code.
 </p>
-<p>Next, you need to add this location to your load path, and <code>require</code> the Org-roam library. Add the following code to your <code>.emacs</code>:
+<p>Next, you need to add this location to your load path, and <code>require</code> the
+Org-roam library. Add the following code to your <code>.emacs</code>:
 </p>
 <div class="lisp">
 <pre class="lisp">(add-to-list 'load-path &quot;/path/to/org/roam&quot;)
 (require 'org-roam)
 </pre></div>
 
-<p>You now have Org-roam installed. However, you don&rsquo;t necessarily have the dependencies that it requires. These include:
+<p>You now have Org-roam installed. However, you don&rsquo;t necessarily have the
+dependencies that it requires. These include:
 </p>
 <ul>
 <li> dash
@@ -669,17 +599,25 @@ Next: <a href="#Post_002dInstallation-Tasks" accesskey="n" rel="next">Post-Insta
 </li><li> emacsql-sqlite3
 </li></ul>
 
-<p>You can install this manually as well, or get the latest version from MELPA. You may wish to use <a href="https://github.com/jwiegley/use-package">use-package</a>, <a href="https://github.com/raxod502/straight.el">straight.el</a>, or some other tool or tools to help manage this.
+<p>You can install this manually as well, or get the latest version from MELPA. You
+may wish to use <a href="https://github.com/jwiegley/use-package">use-package</a>, <a href="https://github.com/raxod502/straight.el">straight.el</a>, or some other tool or tools to help
+manage this.
 </p>
-<p>If you would like to install the manual for access from Emacs&rsquo; built-in Info system, you&rsquo;ll need to compile the .texi source file, and install it in an appropriate location.
+<p>If you would like to install the manual for access from Emacs&rsquo; built-in Info
+system, you&rsquo;ll need to compile the .texi source file, and install it in an
+appropriate location.
 </p>
-<p>To compile the .texi source file, from a terminal navigate to the <code>/doc</code> subdirectory of the Org-roam repository, and run the following:
+<p>To compile the .texi source file, from a terminal navigate to the <code>/doc</code>
+subdirectory of the Org-roam repository, and run the following:
 </p>
 <div class="example">
 <pre class="example">make infodir=/path/to/my/info/files install-info
 </pre></div>
 
-<p>Where <code>/path/to/my/info/files</code> is the location where you keep info files. This target directory needs to be stored in the variable &lsquo;Info-default-directory-list&lsquo;. If you aren&rsquo;t using one of the default info locations, you can configure this with the following in your <code>.emacs</code> file:
+<p>Where <code>/path/to/my/info/files</code> is the location where you keep info files. This
+target directory needs to be stored in the variable
+&lsquo;Info-default-directory-list&lsquo;. If you aren&rsquo;t using one of the default info
+locations, you can configure this with the following in your <code>.emacs</code> file:
 </p>
 <div class="lisp">
 <pre class="lisp">(require 'info)
@@ -697,9 +635,11 @@ Next: <a href="#Post_002dInstallation-Tasks" accesskey="n" rel="next">Post-Insta
 </li><li> <em>usr/local/share/info</em>
 </li></ul>
 
-<p>If you do this, you&rsquo;ll need to make sure you have write-access to that location, or run the above <code>make</code> command as root.
+<p>If you do this, you&rsquo;ll need to make sure you have write-access to that location,
+or run the above <code>make</code> command as root.
 </p>
-<p>Now that the info file is ready, you need to add it to the corresponding <code>dir</code> file:
+<p>Now that the info file is ready, you need to add it to the corresponding <code>dir</code>
+file:
 </p>
 <div class="example">
 <pre class="example">install-info /path/to/my/info/files/org-roam.info /path/to/my/info/files/dir
@@ -709,7 +649,7 @@ Next: <a href="#Post_002dInstallation-Tasks" accesskey="n" rel="next">Post-Insta
 <a name="Post_002dInstallation-Tasks"></a>
 <div class="header">
 <p>
-Previous: <a href="#Installing-from-the-Git-Repository" accesskey="p" rel="prev">Installing from the Git Repository</a>, Up: <a href="#Installation" accesskey="u" rel="up">Installation</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Previous: <a href="#Installing-from-the-Git-Repository" accesskey="p" rel="prev">Installing from the Git Repository</a>, Up: <a href="#Installation" accesskey="u" rel="up">Installation</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Post_002dInstallation-Tasks-1"></a>
 <h3 class="section">4.4 Post-Installation Tasks</h3>
@@ -735,7 +675,7 @@ your Emacs configuration:
 <a name="Getting-Started"></a>
 <div class="header">
 <p>
-Next: <a href="#Anatomy-of-an-Org_002droam-File" accesskey="n" rel="next">Anatomy of an Org-roam File</a>, Previous: <a href="#Installation" accesskey="p" rel="prev">Installation</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Anatomy-of-an-Org_002droam-File" accesskey="n" rel="next">Anatomy of an Org-roam File</a>, Previous: <a href="#Installation" accesskey="p" rel="prev">Installation</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Getting-Started-1"></a>
 <h2 class="chapter">5 Getting Started</h2>
@@ -811,7 +751,7 @@ Protocol</a>).
 <a name="Anatomy-of-an-Org_002droam-File"></a>
 <div class="header">
 <p>
-Next: <a href="#The-Templating-System" accesskey="n" rel="next">The Templating System</a>, Previous: <a href="#Getting-Started" accesskey="p" rel="prev">Getting Started</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#The-Templating-System" accesskey="n" rel="next">The Templating System</a>, Previous: <a href="#Getting-Started" accesskey="p" rel="prev">Getting Started</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Anatomy-of-an-Org_002droam-File-1"></a>
 <h2 class="chapter">6 Anatomy of an Org-roam File</h2>
@@ -834,7 +774,7 @@ to effective use of Org-roam.
 <a name="Titles"></a>
 <div class="header">
 <p>
-Next: <a href="#Tags" accesskey="n" rel="next">Tags</a>, Up: <a href="#Anatomy-of-an-Org_002droam-File" accesskey="u" rel="up">Anatomy of an Org-roam File</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Tags" accesskey="n" rel="next">Tags</a>, Up: <a href="#Anatomy-of-an-Org_002droam-File" accesskey="u" rel="up">Anatomy of an Org-roam File</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Titles-1"></a>
 <h3 class="section">6.1 Titles</h3>
@@ -888,21 +828,23 @@ is used in place of the titles for completions.
 <a name="Tags"></a>
 <div class="header">
 <p>
-Next: <a href="#File-Refs" accesskey="n" rel="next">File Refs</a>, Previous: <a href="#Titles" accesskey="p" rel="prev">Titles</a>, Up: <a href="#Anatomy-of-an-Org_002droam-File" accesskey="u" rel="up">Anatomy of an Org-roam File</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#File-Refs" accesskey="n" rel="next">File Refs</a>, Previous: <a href="#Titles" accesskey="p" rel="prev">Titles</a>, Up: <a href="#Anatomy-of-an-Org_002droam-File" accesskey="u" rel="up">Anatomy of an Org-roam File</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Tags-1"></a>
 <h3 class="section">6.2 Tags</h3>
 
 <p>Tags are used as meta-data for files: they facilitate interactions with notes
 where titles are insufficient. For example, tags allow for categorization of
-notes: differentiating between bibliographical and structure notes during interactive commands.
+notes: differentiating between bibliographical and structure notes during
+interactive commands.
 </p>
 <p>Org-roam calls <code>org-roam--extract-tags</code> to extract tags from files. It uses the
 variable <code>org-roam-tag-sources</code>, to control how tags are extracted. The tag
 extraction methods supported are:
 </p>
 <ul>
-<li> <code>'prop</code>: This extracts tags from the <code>#+roam_tags</code> property. Tags are space delimited, and can be multi-word using double quotes.
+<li> <code>'prop</code>: This extracts tags from the <code>#+roam_tags</code> property. Tags are space
+delimited, and can be multi-word using double quotes.
 
 </li><li> <code>'all-directories</code>: All sub-directories relative to <code>org-roam-directory</code> are
 extracted as tags. That is, if a file is located at relative path
@@ -933,24 +875,25 @@ accepts the absolute file path as its argument. See
 <a name="File-Refs"></a>
 <div class="header">
 <p>
-Previous: <a href="#Tags" accesskey="p" rel="prev">Tags</a>, Up: <a href="#Anatomy-of-an-Org_002droam-File" accesskey="u" rel="up">Anatomy of an Org-roam File</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Previous: <a href="#Tags" accesskey="p" rel="prev">Tags</a>, Up: <a href="#Anatomy-of-an-Org_002droam-File" accesskey="u" rel="up">Anatomy of an Org-roam File</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="File-Refs-1"></a>
 <h3 class="section">6.3 File Refs</h3>
 
-<p>Refs are unique identifiers for files. For example, a note for a website may contain a ref:
+<p>Refs are unique identifiers for files. For example, a note for a website may
+contain a ref:
 </p>
 <div class="example">
 <pre class="example">#+title: Google
 #+roam_key: https://www.google.com/
 </pre></div>
 
-<p>These keys allow references to the key to show up in the backlinks buffer. For instance,
-with the example above, if another file then links to <a href="https://www.google.com">https://www.google.com</a>, that will
-show up as a “Ref Backlink”.
+<p>These keys allow references to the key to show up in the backlinks buffer. For
+instance, with the example above, if another file then links to
+<a href="https://www.google.com">https://www.google.com</a>, that will show up as a “Ref Backlink”.
 </p>
-<p>These keys also come in useful for when taking website notes, using the <code>roam-ref</code> protocol
- (see <a href="#Roam-Protocol">Roam Protocol</a>).
+<p>These keys also come in useful for when taking website notes, using the
+ <code>roam-ref</code> protocol (see <a href="#Roam-Protocol">Roam Protocol</a>).
 </p>
 <p><a href="https://github.com/jkitchin/org-ref">org-ref</a> citation keys can also be used as refs:
 </p>
@@ -963,15 +906,15 @@ show up as a “Ref Backlink”.
 <img src="images/org-ref-citelink.png" alt="images/org-ref-citelink">
 
 <div class="float-caption"><p><strong>Figure: </strong>org-ref-citelink</p></div></div>
-<p>You may assign multiple refs to a single file, for example when you want multiple papers
-in a series to share the same note, or an article has a citation key and a URL at the same
-time.
+<p>You may assign multiple refs to a single file, for example when you want
+multiple papers in a series to share the same note, or an article has a citation
+key and a URL at the same time.
 </p>
 <hr>
 <a name="The-Templating-System"></a>
 <div class="header">
 <p>
-Next: <a href="#Concepts-and-Configuration" accesskey="n" rel="next">Concepts and Configuration</a>, Previous: <a href="#Anatomy-of-an-Org_002droam-File" accesskey="p" rel="prev">Anatomy of an Org-roam File</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Concepts-and-Configuration" accesskey="n" rel="next">Concepts and Configuration</a>, Previous: <a href="#Anatomy-of-an-Org_002droam-File" accesskey="p" rel="prev">Anatomy of an Org-roam File</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="The-Templating-System-1"></a>
 <h2 class="chapter">7 The Templating System</h2>
@@ -1014,7 +957,7 @@ will be no prompt for template selection.
 <a name="Template-Walkthrough"></a>
 <div class="header">
 <p>
-Next: <a href="#Org_002droam-Template-Expansion" accesskey="n" rel="next">Org-roam Template Expansion</a>, Up: <a href="#The-Templating-System" accesskey="u" rel="up">The Templating System</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Org_002droam-Template-Expansion" accesskey="n" rel="next">Org-roam Template Expansion</a>, Up: <a href="#The-Templating-System" accesskey="u" rel="up">The Templating System</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Template-Walkthrough-1"></a>
 <h3 class="section">7.1 Template Walkthrough</h3>
@@ -1031,8 +974,8 @@ the default template, reproduced below.
 </pre></div>
 
 <ul>
-<li> The template has short key <code>&quot;d&quot;</code>. If you have only one template,
-org-roam automatically chooses this template for you.
+<li> The template has short key <code>&quot;d&quot;</code>. If you have only one template, org-roam
+automatically chooses this template for you.
 
 </li><li> The template is given a description of <code>&quot;default&quot;</code>.
 
@@ -1042,8 +985,7 @@ org-roam automatically chooses this template for you.
 </li><li> <code>(function org-roam--capture-get-point)</code> should not be changed.
 
 </li><li> <code>&quot;%?&quot;</code> is the template inserted on each call to <code>org-roam-capture--capture</code>.
-This template means don&rsquo;t insert any content, but place the cursor
-here.
+This template means don&rsquo;t insert any content, but place the cursor here.
 
 </li><li> <code>:file-name</code> is the file-name template for a new note, if it doesn&rsquo;t yet
 exist. This creates a file at path that looks like
@@ -1066,7 +1008,7 @@ file, rather than narrowing to just the entry.
 <a name="Org_002droam-Template-Expansion"></a>
 <div class="header">
 <p>
-Previous: <a href="#Template-Walkthrough" accesskey="p" rel="prev">Template Walkthrough</a>, Up: <a href="#The-Templating-System" accesskey="u" rel="up">The Templating System</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Previous: <a href="#Template-Walkthrough" accesskey="p" rel="prev">Template Walkthrough</a>, Up: <a href="#The-Templating-System" accesskey="u" rel="up">The Templating System</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Org_002droam-Template-Expansion-1"></a>
 <h3 class="section">7.2 Org-roam Template Expansion</h3>
@@ -1083,9 +1025,9 @@ provided title. <code>${title}</code> is then expanded into the provided title d
 org-capture process. Any variables that do not contain strings, are prompted for
 values using <code>completing-read</code>.
 </p>
-<p>After doing this expansion, the org-capture&rsquo;s template expansion system
-is used to fill up the rest of the template. You may read up more on
-this on <a href="https://orgmode.org/manual/Template-expansion.html#Template-expansion">org-capture&rsquo;s documentation page</a>.
+<p>After doing this expansion, the org-capture&rsquo;s template expansion system is used
+to fill up the rest of the template. You may read up more on this on
+<a href="https://orgmode.org/manual/Template-expansion.html#Template-expansion">org-capture&rsquo;s documentation page</a>.
 </p>
 <p>To illustrate this dual expansion process, take for example the template string:
 <code>&quot;%&lt;%Y%m%d%H%M%S&gt;-${title}&quot;</code>, with the title <code>&quot;Foo&quot;</code>. The template is first
@@ -1109,17 +1051,17 @@ directly to provide its third argument to specify UTC.
 <a name="Concepts-and-Configuration"></a>
 <div class="header">
 <p>
-Next: <a href="#Inserting-Links" accesskey="n" rel="next">Inserting Links</a>, Previous: <a href="#The-Templating-System" accesskey="p" rel="prev">The Templating System</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Inserting-Links" accesskey="n" rel="next">Inserting Links</a>, Previous: <a href="#The-Templating-System" accesskey="p" rel="prev">The Templating System</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Concepts-and-Configuration-1"></a>
 <h2 class="chapter">8 Concepts and Configuration</h2>
 
-<p>The number of configuration options is deliberately kept small, to keep
-the Org-roam codebase manageable. However, we attempt to accommodate as
-many usage styles as possible.
+<p>The number of configuration options is deliberately kept small, to keep the
+Org-roam codebase manageable. However, we attempt to accommodate as many usage
+styles as possible.
 </p>
-<p>All of Org-roam&rsquo;s customization options can be viewed via
-<code>M-x customize-group org-roam</code>.
+<p>All of Org-roam&rsquo;s customization options can be viewed via <code>M-x customize-group
+org-roam</code>.
 </p>
 <table class="menu" border="0" cellspacing="0">
 <tr><td align="left" valign="top">&bull; <a href="#Directories-and-Files" accesskey="1">Directories and Files</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
@@ -1136,7 +1078,7 @@ many usage styles as possible.
 <a name="Directories-and-Files"></a>
 <div class="header">
 <p>
-Next: <a href="#The-Org_002droam-Buffer" accesskey="n" rel="next">The Org-roam Buffer</a>, Up: <a href="#Concepts-and-Configuration" accesskey="u" rel="up">Concepts and Configuration</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#The-Org_002droam-Buffer" accesskey="n" rel="next">The Org-roam Buffer</a>, Up: <a href="#Concepts-and-Configuration" accesskey="u" rel="up">Concepts and Configuration</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Directories-and-Files-1"></a>
 <h3 class="section">8.1 Directories and Files</h3>
@@ -1170,7 +1112,7 @@ with multiple Org-roam instances.
 <a name="The-Org_002droam-Buffer"></a>
 <div class="header">
 <p>
-Next: <a href="#Org_002droam-Files" accesskey="n" rel="next">Org-roam Files</a>, Previous: <a href="#Directories-and-Files" accesskey="p" rel="prev">Directories and Files</a>, Up: <a href="#Concepts-and-Configuration" accesskey="u" rel="up">Concepts and Configuration</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Org_002droam-Files" accesskey="n" rel="next">Org-roam Files</a>, Previous: <a href="#Directories-and-Files" accesskey="p" rel="prev">Directories and Files</a>, Up: <a href="#Concepts-and-Configuration" accesskey="u" rel="up">Concepts and Configuration</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="The-Org_002droam-Buffer-1"></a>
 <h3 class="section">8.2 The Org-roam Buffer</h3>
@@ -1219,7 +1161,7 @@ Next: <a href="#Org_002droam-Files" accesskey="n" rel="next">Org-roam Files</a>,
 <a name="Org_002droam-Files"></a>
 <div class="header">
 <p>
-Next: <a href="#Org_002droam-Faces" accesskey="n" rel="next">Org-roam Faces</a>, Previous: <a href="#The-Org_002droam-Buffer" accesskey="p" rel="prev">The Org-roam Buffer</a>, Up: <a href="#Concepts-and-Configuration" accesskey="u" rel="up">Concepts and Configuration</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Org_002droam-Faces" accesskey="n" rel="next">Org-roam Faces</a>, Previous: <a href="#The-Org_002droam-Buffer" accesskey="p" rel="prev">The Org-roam Buffer</a>, Up: <a href="#Concepts-and-Configuration" accesskey="u" rel="up">Concepts and Configuration</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Org_002droam-Files-1"></a>
 <h3 class="section">8.3 Org-roam Files</h3>
@@ -1231,7 +1173,7 @@ system. The templating system is customizable (see <a href="#The-Templating-Syst
 <a name="Org_002droam-Faces"></a>
 <div class="header">
 <p>
-Previous: <a href="#Org_002droam-Files" accesskey="p" rel="prev">Org-roam Files</a>, Up: <a href="#Concepts-and-Configuration" accesskey="u" rel="up">Concepts and Configuration</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Previous: <a href="#Org_002droam-Files" accesskey="p" rel="prev">Org-roam Files</a>, Up: <a href="#Concepts-and-Configuration" accesskey="u" rel="up">Concepts and Configuration</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Org_002droam-Faces-1"></a>
 <h3 class="section">8.4 Org-roam Faces</h3>
@@ -1259,7 +1201,7 @@ links to files or IDs that cannot be found.
 <a name="Inserting-Links"></a>
 <div class="header">
 <p>
-Next: <a href="#Navigating-Around" accesskey="n" rel="next">Navigating Around</a>, Previous: <a href="#Concepts-and-Configuration" accesskey="p" rel="prev">Concepts and Configuration</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Navigating-Around" accesskey="n" rel="next">Navigating Around</a>, Previous: <a href="#Concepts-and-Configuration" accesskey="p" rel="prev">Concepts and Configuration</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Inserting-Links-1"></a>
 <h2 class="chapter">9 Inserting Links</h2>
@@ -1281,16 +1223,19 @@ registers this link type, and interprets the path as follows:
 <ul>
 <li> <code>[[roam:title]]</code>links to an Org-roam file with title or alias &ldquo;title&rdquo;
 
-</li><li> <code>[[roam:*headline]]</code>links to the headline &ldquo;headline&rdquo; in the current Org-roam file
+</li><li> <code>[[roam:*headline]]</code>links to the headline &ldquo;headline&rdquo; in the current
+Org-roam file
 
-</li><li> <code>[[roam:title*headline]]</code>links to the headline &ldquo;headline&rdquo; in the Org-roam file with title or alias &ldquo;title&rdquo;
+</li><li> <code>[[roam:title*headline]]</code>links to the headline &ldquo;headline&rdquo; in the Org-roam
+file with title or alias &ldquo;title&rdquo;
 </li></ul>
 
 <p><code>roam</code> links support auto-completion via <code>completion-at-point</code>: simply call
 <code>completion-at-point</code> within a roam link. Users of <code>company-mode</code> may want to
 prepend <code>company-capf</code> to the beginning of variable <code>company-backends</code>.
 </p>
-<p>To easily insert <code>roam</code> links, one may wish to use a package like <a href="https://github.com/emacsorphanage/key-chord/">key-chord</a>. In the following example, typing &ldquo;[[&rdquo; will insert a stub <code>roam</code> link:
+<p>To easily insert <code>roam</code> links, one may wish to use a package like <a href="https://github.com/emacsorphanage/key-chord/">key-chord</a>. In
+the following example, typing &ldquo;[[&rdquo; will insert a stub <code>roam</code> link:
 </p>
 <div class="lisp">
 <pre class="lisp">(key-chord-define org-mode-map &quot;[[&quot; #'my/insert-roam-link)
@@ -1333,7 +1278,7 @@ harder to edit. Defaults to <code>t</code>.
 <a name="Navigating-Around"></a>
 <div class="header">
 <p>
-Next: <a href="#Encryption" accesskey="n" rel="next">Encryption</a>, Previous: <a href="#Inserting-Links" accesskey="p" rel="prev">Inserting Links</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Encryption" accesskey="n" rel="next">Encryption</a>, Previous: <a href="#Inserting-Links" accesskey="p" rel="prev">Inserting Links</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Navigating-Around-1"></a>
 <h2 class="chapter">10 Navigating Around</h2>
@@ -1347,7 +1292,7 @@ Next: <a href="#Encryption" accesskey="n" rel="next">Encryption</a>, Previous: <
 <a name="Index-File"></a>
 <div class="header">
 <p>
-Up: <a href="#Navigating-Around" accesskey="u" rel="up">Navigating Around</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Up: <a href="#Navigating-Around" accesskey="u" rel="up">Navigating Around</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Index-File-1"></a>
 <h3 class="section">10.1 Index File</h3>
@@ -1380,7 +1325,7 @@ title is <code>&quot;Index&quot;</code>.
 <a name="Encryption"></a>
 <div class="header">
 <p>
-Next: <a href="#Graphing" accesskey="n" rel="next">Graphing</a>, Previous: <a href="#Navigating-Around" accesskey="p" rel="prev">Navigating Around</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Graphing" accesskey="n" rel="next">Graphing</a>, Previous: <a href="#Navigating-Around" accesskey="p" rel="prev">Navigating Around</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Encryption-1"></a>
 <h2 class="chapter">11 Encryption</h2>
@@ -1390,21 +1335,21 @@ GPG), which can be enabled for all new files by setting <code>org-roam-encrypt-f
 to <code>t</code>. When enabled, new files are created with the <code>.org.gpg</code> extension and
 decryption are handled automatically by EasyPG.
 </p>
-<p>Note that Emacs will prompt for a password for encrypted files during
-cache updates if it requires reading the encrypted file. To reduce the
-number of password prompts, you may wish to cache the password.
+<p>Note that Emacs will prompt for a password for encrypted files during cache
+updates if it requires reading the encrypted file. To reduce the number of
+password prompts, you may wish to cache the password.
 </p>
 <dl>
 <dt><a name="index-org_002droam_002dencrypt_002dfiles"></a>User Option: <strong>org-roam-encrypt-files</strong></dt>
 <dd>
-<p>Whether to encrypt new files.  If true, create files with .org.gpg extension.
+<p>Whether to encrypt new files. If true, create files with .org.gpg extension.
 </p></dd></dl>
 
 <hr>
 <a name="Graphing"></a>
 <div class="header">
 <p>
-Next: <a href="#Org_002droam-Completion-System" accesskey="n" rel="next">Org-roam Completion System</a>, Previous: <a href="#Encryption" accesskey="p" rel="prev">Encryption</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Org_002droam-Completion-System" accesskey="n" rel="next">Org-roam Completion System</a>, Previous: <a href="#Encryption" accesskey="p" rel="prev">Encryption</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Graphing-1"></a>
 <h2 class="chapter">12 Graphing</h2>
@@ -1440,7 +1385,8 @@ ARG may be any of the following values:
 <dl>
 <dt><a name="index-org_002droam_002dgraph_002dexecutable"></a>User Option: <strong>org-roam-graph-executable</strong></dt>
 <dd>
-<p>Path to the graphing executable (in this case, Graphviz). Set this if Org-roam is unable to find the Graphviz executable on your system.
+<p>Path to the graphing executable (in this case, Graphviz). Set this if Org-roam
+is unable to find the Graphviz executable on your system.
 </p>
 <p>You may also choose to use <code>neato</code> in place of <code>dot</code>, which generates a more
 compact graph layout.
@@ -1449,7 +1395,8 @@ compact graph layout.
 <dl>
 <dt><a name="index-org_002droam_002dgraph_002dviewer"></a>User Option: <strong>org-roam-graph-viewer</strong></dt>
 <dd>
-<p>Org-roam defaults to using Firefox (located on PATH) to view the SVG, but you may choose to set it to:
+<p>Org-roam defaults to using Firefox (located on PATH) to view the SVG, but you
+may choose to set it to:
 </p>
 <ul>
 <li> A string, which is a path to the program used
@@ -1459,7 +1406,8 @@ compact graph layout.
 
 <p><code>nil</code> uses <code>view-file</code> to view the graph.
 </p>
-<p>If you are using WSL2 and would like to open the graph in Windows, you can use the second option to set the browser and network file path:
+<p>If you are using WSL2 and would like to open the graph in Windows, you can use
+the second option to set the browser and network file path:
 </p>
 <div class="lisp">
 <pre class="lisp">(setq org-roam-graph-viewer
@@ -1480,12 +1428,14 @@ compact graph layout.
 <a name="Graph-Options"></a>
 <div class="header">
 <p>
-Next: <a href="#Excluding-Nodes-and-Edges" accesskey="n" rel="next">Excluding Nodes and Edges</a>, Up: <a href="#Graphing" accesskey="u" rel="up">Graphing</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Excluding-Nodes-and-Edges" accesskey="n" rel="next">Excluding Nodes and Edges</a>, Up: <a href="#Graphing" accesskey="u" rel="up">Graphing</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Graph-Options-1"></a>
 <h3 class="section">12.1 Graph Options</h3>
 
-<p>Graphviz provides many options for customizing the graph output, and Org-roam supports some of them. See <a href="https://graphviz.gitlab.io/_pages/doc/info/attrs.html">https://graphviz.gitlab.io/_pages/doc/info/attrs.html</a> for customizable options.
+<p>Graphviz provides many options for customizing the graph output, and Org-roam
+supports some of them. See <a href="https://graphviz.gitlab.io/_pages/doc/info/attrs.html">https://graphviz.gitlab.io/_pages/doc/info/attrs.html</a>
+for customizable options.
 </p>
 <dl>
 <dt><a name="index-org_002droam_002dgraph_002dextra_002dconfig"></a>User Option: <strong>org-roam-graph-extra-config</strong></dt>
@@ -1519,7 +1469,7 @@ Example: <code>'((&quot;color&quot; . &quot;red&quot;))</code>
 <a name="Excluding-Nodes-and-Edges"></a>
 <div class="header">
 <p>
-Previous: <a href="#Graph-Options" accesskey="p" rel="prev">Graph Options</a>, Up: <a href="#Graphing" accesskey="u" rel="up">Graphing</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Previous: <a href="#Graph-Options" accesskey="p" rel="prev">Graph Options</a>, Up: <a href="#Graphing" accesskey="u" rel="up">Graphing</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Excluding-Nodes-and-Edges-1"></a>
 <h3 class="section">12.2 Excluding Nodes and Edges</h3>
@@ -1548,7 +1498,7 @@ are excluded.
 <a name="Org_002droam-Completion-System"></a>
 <div class="header">
 <p>
-Next: <a href="#Roam-Protocol" accesskey="n" rel="next">Roam Protocol</a>, Previous: <a href="#Graphing" accesskey="p" rel="prev">Graphing</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Roam-Protocol" accesskey="n" rel="next">Roam Protocol</a>, Previous: <a href="#Graphing" accesskey="p" rel="prev">Graphing</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Org_002droam-Completion-System-1"></a>
 <h2 class="chapter">13 Org-roam Completion System</h2>
@@ -1577,13 +1527,13 @@ commands, set:
 <a name="Roam-Protocol"></a>
 <div class="header">
 <p>
-Next: <a href="#Daily_002dnotes" accesskey="n" rel="next">Daily-notes</a>, Previous: <a href="#Org_002droam-Completion-System" accesskey="p" rel="prev">Org-roam Completion System</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Daily_002dnotes" accesskey="n" rel="next">Daily-notes</a>, Previous: <a href="#Org_002droam-Completion-System" accesskey="p" rel="prev">Org-roam Completion System</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Roam-Protocol-1"></a>
 <h2 class="chapter">14 Roam Protocol</h2>
 
-<p>Org-roam extends <code>org-protocol</code> with 2 protocols: the <code>roam-file</code>
-and <code>roam-ref</code> protocols.
+<p>Org-roam extends <code>org-protocol</code> with 2 protocols: the <code>roam-file</code> and <code>roam-ref</code>
+protocols.
 </p>
 <table class="menu" border="0" cellspacing="0">
 <tr><td align="left" valign="top">&bull; <a href="#Installation-_00281_0029" accesskey="1">Installation</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
@@ -1598,12 +1548,13 @@ and <code>roam-ref</code> protocols.
 <a name="Installation-_00281_0029"></a>
 <div class="header">
 <p>
-Next: <a href="#The-roam_002dfile-protocol" accesskey="n" rel="next">The roam-file protocol</a>, Up: <a href="#Roam-Protocol" accesskey="u" rel="up">Roam Protocol</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#The-roam_002dfile-protocol" accesskey="n" rel="next">The roam-file protocol</a>, Up: <a href="#Roam-Protocol" accesskey="u" rel="up">Roam Protocol</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Installation-2"></a>
 <h3 class="section">14.1 Installation</h3>
 
-<p>To enable Org-roam&rsquo;s protocol extensions, you have to add the following to your init file:
+<p>To enable Org-roam&rsquo;s protocol extensions, you have to add the following to your
+init file:
 </p>
 <div class="lisp">
 <pre class="lisp">(require 'org-roam-protocol)
@@ -1614,7 +1565,8 @@ Next: <a href="#The-roam_002dfile-protocol" accesskey="n" rel="next">The roam-fi
 <p>We will also need to create a desktop application for <code>emacsclient</code>. The
 instructions for various platforms are shown below.
 </p>
-<p>For Linux users, create a desktop application in <code>~/.local/share/applications/org-protocol.desktop</code>:
+<p>For Linux users, create a desktop application in
+<code>~/.local/share/applications/org-protocol.desktop</code>:
 </p>
 <div class="example">
 <pre class="example">[Desktop Entry]
@@ -1633,9 +1585,9 @@ running in your shell:
 <pre class="example">xdg-mime default org-protocol.desktop x-scheme-handler/org-protocol
 </pre></div>
 
-<p>To disable the &ldquo;confirm&rdquo; prompt in Chrome, you can also make Chrome
-show a checkbox to tick, so that the <code>Org-Protocol Client</code> app will be used
-without confirmation. To do this, run in a shell:
+<p>To disable the &ldquo;confirm&rdquo; prompt in Chrome, you can also make Chrome show a
+checkbox to tick, so that the <code>Org-Protocol Client</code> app will be used without
+confirmation. To do this, run in a shell:
 </p>
 <div class="example">
 <pre class="example">sudo mkdir -p /etc/opt/chrome/policies/managed/
@@ -1733,19 +1685,21 @@ the default handler instead, run:
 @=&quot;\&quot;C:\\Windows\\System32\\wsl.exe\&quot; emacsclient \&quot;%1\&quot;&quot;
 </pre></div>
 
-<p>The above will forward the protocol to WSL. If you run Emacs natively on Windows, replace the last line with:
+<p>The above will forward the protocol to WSL. If you run Emacs natively on
+Windows, replace the last line with:
 </p>
 <div class="example">
 <pre class="example">@=&quot;\&quot;c:\\path\\to\\emacs\\bin\\emacsclientw.exe\&quot;  \&quot;%1\&quot;&quot;
 </pre></div>
 
-<p>After executing the .reg file, the protocol is registered and you can delete the file.
+<p>After executing the .reg file, the protocol is registered and you can delete the
+file.
 </p>
 <hr>
 <a name="The-roam_002dfile-protocol"></a>
 <div class="header">
 <p>
-Next: <a href="#The-roam_002dref-protocol" accesskey="n" rel="next">The roam-ref protocol</a>, Previous: <a href="#Installation-_00281_0029" accesskey="p" rel="prev">Installation (1)</a>, Up: <a href="#Roam-Protocol" accesskey="u" rel="up">Roam Protocol</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#The-roam_002dref-protocol" accesskey="n" rel="next">The roam-ref protocol</a>, Previous: <a href="#Installation-_00281_0029" accesskey="p" rel="prev">Installation (1)</a>, Up: <a href="#Roam-Protocol" accesskey="u" rel="up">Roam Protocol</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="The-roam_002dfile-protocol-1"></a>
 <h3 class="section">14.2 The roam-file protocol</h3>
@@ -1758,7 +1712,7 @@ in the generated graph.
 <a name="The-roam_002dref-protocol"></a>
 <div class="header">
 <p>
-Previous: <a href="#The-roam_002dfile-protocol" accesskey="p" rel="prev">The roam-file protocol</a>, Up: <a href="#Roam-Protocol" accesskey="u" rel="up">Roam Protocol</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Previous: <a href="#The-roam_002dfile-protocol" accesskey="p" rel="prev">The roam-file protocol</a>, Up: <a href="#Roam-Protocol" accesskey="u" rel="up">Roam Protocol</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="The-roam_002dref-protocol-1"></a>
 <h3 class="section">14.3 The roam-ref protocol</h3>
@@ -1794,7 +1748,7 @@ should contain a <code>#+roam_key: ${ref}</code> in it.
 <a name="Daily_002dnotes"></a>
 <div class="header">
 <p>
-Next: <a href="#Diagnosing-and-Repairing-Files" accesskey="n" rel="next">Diagnosing and Repairing Files</a>, Previous: <a href="#Roam-Protocol" accesskey="p" rel="prev">Roam Protocol</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Diagnosing-and-Repairing-Files" accesskey="n" rel="next">Diagnosing and Repairing Files</a>, Previous: <a href="#Roam-Protocol" accesskey="p" rel="prev">Roam Protocol</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Daily_002dnotes-1"></a>
 <h2 class="chapter">15 Daily-notes</h2>
@@ -1815,7 +1769,7 @@ Next: <a href="#Diagnosing-and-Repairing-Files" accesskey="n" rel="next">Diagnos
 <a name="Configuration"></a>
 <div class="header">
 <p>
-Next: <a href="#Capturing-and-finding-daily_002dnotes" accesskey="n" rel="next">Capturing and finding daily-notes</a>, Up: <a href="#Daily_002dnotes" accesskey="u" rel="up">Daily-notes</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Capturing-and-finding-daily_002dnotes" accesskey="n" rel="next">Capturing and finding daily-notes</a>, Up: <a href="#Daily_002dnotes" accesskey="u" rel="up">Daily-notes</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Configuration-1"></a>
 <h3 class="section">15.1 Configuration</h3>
@@ -1848,8 +1802,8 @@ Next: <a href="#Capturing-and-finding-daily_002dnotes" accesskey="n" rel="next">
 </pre></div>
 
 <p>Make sure that <code>org-roam-dailies-directory</code> appears in <code>:file-name</code> for your
-notes to be recognized as daily-notes. You can have different templates
-placing their notes in different directories, but the one in
+notes to be recognized as daily-notes. You can have different templates placing
+their notes in different directories, but the one in
 <code>org-roam-dailies-directory</code> will be considered as the main one in commands.
 </p>
 <p>See <a href="#The-Templating-System">The Templating System</a> for creating new
@@ -1874,14 +1828,14 @@ specifying the outline-path to a heading:
 </pre></div>
 
 <p>The template <code>l</code> will put its notes under the heading ‘Lab notes’, and the
-template <code>j</code> will put its notes under the heading ‘Journal’.  When you use
+template <code>j</code> will put its notes under the heading ‘Journal’. When you use
 <code>:olp</code>, make sure that the headings are present in <code>:head</code>.
 </p>
 <hr>
 <a name="Capturing-and-finding-daily_002dnotes"></a>
 <div class="header">
 <p>
-Next: <a href="#Navigation" accesskey="n" rel="next">Navigation</a>, Previous: <a href="#Configuration" accesskey="p" rel="prev">Configuration</a>, Up: <a href="#Daily_002dnotes" accesskey="u" rel="up">Daily-notes</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Navigation" accesskey="n" rel="next">Navigation</a>, Previous: <a href="#Configuration" accesskey="p" rel="prev">Configuration</a>, Up: <a href="#Daily_002dnotes" accesskey="u" rel="up">Daily-notes</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Capturing-and-finding-daily_002dnotes-1"></a>
 <h3 class="section">15.2 Capturing and finding daily-notes</h3>
@@ -1941,7 +1895,7 @@ creating an entry.
 <a name="Navigation"></a>
 <div class="header">
 <p>
-Previous: <a href="#Capturing-and-finding-daily_002dnotes" accesskey="p" rel="prev">Capturing and finding daily-notes</a>, Up: <a href="#Daily_002dnotes" accesskey="u" rel="up">Daily-notes</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Previous: <a href="#Capturing-and-finding-daily_002dnotes" accesskey="p" rel="prev">Capturing and finding daily-notes</a>, Up: <a href="#Daily_002dnotes" accesskey="u" rel="up">Daily-notes</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Navigation-1"></a>
 <h3 class="section">15.3 Navigation</h3>
@@ -1970,7 +1924,7 @@ Previous: <a href="#Capturing-and-finding-daily_002dnotes" accesskey="p" rel="pr
 <a name="Diagnosing-and-Repairing-Files"></a>
 <div class="header">
 <p>
-Next: <a href="#Finding-Unlinked-References" accesskey="n" rel="next">Finding Unlinked References</a>, Previous: <a href="#Daily_002dnotes" accesskey="p" rel="prev">Daily-notes</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Finding-Unlinked-References" accesskey="n" rel="next">Finding Unlinked References</a>, Previous: <a href="#Daily_002dnotes" accesskey="p" rel="prev">Daily-notes</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Diagnosing-and-Repairing-Files-1"></a>
 <h2 class="chapter">16 Diagnosing and Repairing Files</h2>
@@ -1987,10 +1941,11 @@ org-roam-doctor</code>, but note that this may take some time.
 the check only for the current buffer.
 </p></dd></dl>
 
-<p>The checks run are defined in <code>org-roam-doctor--checkers</code>. By default, there are checkers for broken links and invalid &lsquo;<samp>#+roam_*</samp>&rsquo; properties.
+<p>The checks run are defined in <code>org-roam-doctor--checkers</code>. By default, there are
+checkers for broken links and invalid &lsquo;<samp>#+roam_*</samp>&rsquo; properties.
 </p>
-<p>Each checker is an instance of <code>org-roam-doctor-checker</code>. To define a checker, use
-<code>make-org-roam-doctor-checker</code>. Here is a sample definition:
+<p>Each checker is an instance of <code>org-roam-doctor-checker</code>. To define a checker,
+use <code>make-org-roam-doctor-checker</code>. Here is a sample definition:
 </p>
 <div class="lisp">
 <pre class="lisp">(make-org-roam-doctor-checker
@@ -2002,10 +1957,10 @@ the check only for the current buffer.
 </pre></div>
 
 <p>The <code>:name</code> property is the name of the function run. The function takes in the
-Org parse tree, and returns a list of <code>(point error-message)</code>. <code>:description</code> is a
-short description of what the checker does. <code>:actions</code> is an alist containing
-elements of the form <code>(char . (prompt . function))</code>. These actions are defined per
-checker, to perform autofixes for the errors. For each error detected,
+Org parse tree, and returns a list of <code>(point error-message)</code>. <code>:description</code> is
+a short description of what the checker does. <code>:actions</code> is an alist containing
+elements of the form <code>(char . (prompt . function))</code>. These actions are defined
+per checker, to perform autofixes for the errors. For each error detected,
 <code>org-roam-doctor</code> will move the point to the current error, and pop-up a help
 window displaying the error message, as well as the list of actions that can be
 taken provided in <code>:actions</code>.
@@ -2014,7 +1969,7 @@ taken provided in <code>:actions</code>.
 <a name="Finding-Unlinked-References"></a>
 <div class="header">
 <p>
-Next: <a href="#Performance-Optimization" accesskey="n" rel="next">Performance Optimization</a>, Previous: <a href="#Diagnosing-and-Repairing-Files" accesskey="p" rel="prev">Diagnosing and Repairing Files</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Performance-Optimization" accesskey="n" rel="next">Performance Optimization</a>, Previous: <a href="#Diagnosing-and-Repairing-Files" accesskey="p" rel="prev">Diagnosing and Repairing Files</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Finding-Unlinked-References-1"></a>
 <h2 class="chapter">17 Finding Unlinked References</h2>
@@ -2040,7 +1995,7 @@ unlinked references within encrypted files.
 <a name="Performance-Optimization"></a>
 <div class="header">
 <p>
-Next: <a href="#Appendix" accesskey="n" rel="next">Appendix</a>, Previous: <a href="#Finding-Unlinked-References" accesskey="p" rel="prev">Finding Unlinked References</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Appendix" accesskey="n" rel="next">Appendix</a>, Previous: <a href="#Finding-Unlinked-References" accesskey="p" rel="prev">Finding Unlinked References</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Performance-Optimization-1"></a>
 <h2 class="chapter">18 Performance Optimization</h2>
@@ -2056,7 +2011,7 @@ Next: <a href="#Appendix" accesskey="n" rel="next">Appendix</a>, Previous: <a hr
 <a name="Profiling-Key-Operations"></a>
 <div class="header">
 <p>
-Next: <a href="#Garbage-Collection" accesskey="n" rel="next">Garbage Collection</a>, Up: <a href="#Performance-Optimization" accesskey="u" rel="up">Performance Optimization</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Garbage-Collection" accesskey="n" rel="next">Garbage Collection</a>, Up: <a href="#Performance-Optimization" accesskey="u" rel="up">Performance Optimization</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="TODO-Profiling-Key-Operations"></a>
 <h3 class="section">18.1 <strong>TODO</strong> Profiling Key Operations</h3>
@@ -2065,13 +2020,14 @@ Next: <a href="#Garbage-Collection" accesskey="n" rel="next">Garbage Collection<
 <a name="Garbage-Collection"></a>
 <div class="header">
 <p>
-Previous: <a href="#Profiling-Key-Operations" accesskey="p" rel="prev">Profiling Key Operations</a>, Up: <a href="#Performance-Optimization" accesskey="u" rel="up">Performance Optimization</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Previous: <a href="#Profiling-Key-Operations" accesskey="p" rel="prev">Profiling Key Operations</a>, Up: <a href="#Performance-Optimization" accesskey="u" rel="up">Performance Optimization</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Garbage-Collection-1"></a>
 <h3 class="section">18.2 Garbage Collection</h3>
 
 <p>During the cache-build process, Org-roam generates a lot of in-memory
-data-structures (such as the Org file&rsquo;s AST), which are discarded after use. These structures are garbage collected at regular intervals (see <a href="https://www.gnu.org/software/emacs/manual/html_mono/elisp.html#Garbage-Collection">(elisp)info:elisp#Garbage Collection</a>).
+data-structures (such as the Org file&rsquo;s AST), which are discarded after use.
+These structures are garbage collected at regular intervals (see <a href="https://www.gnu.org/software/emacs/manual/html_mono/elisp.html#Garbage-Collection">(elisp)info:elisp#Garbage Collection</a>).
 </p>
 <p>Org-roam provides the option <code>org-roam-db-gc-threshold</code> to temporarily change
 the threshold value for GC to be triggered during these memory-intensive
@@ -2086,7 +2042,7 @@ operations. To reduce the number of garbage collection processes, one may set
 <a name="Appendix"></a>
 <div class="header">
 <p>
-Next: <a href="#FAQ" accesskey="n" rel="next">FAQ</a>, Previous: <a href="#Performance-Optimization" accesskey="p" rel="prev">Performance Optimization</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#FAQ" accesskey="n" rel="next">FAQ</a>, Previous: <a href="#Performance-Optimization" accesskey="p" rel="prev">Performance Optimization</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Appendix-1"></a>
 <h2 class="chapter">19 Appendix</h2>
@@ -2102,7 +2058,7 @@ Next: <a href="#FAQ" accesskey="n" rel="next">FAQ</a>, Previous: <a href="#Perfo
 <a name="Note_002dtaking-Workflows"></a>
 <div class="header">
 <p>
-Next: <a href="#Ecosystem" accesskey="n" rel="next">Ecosystem</a>, Up: <a href="#Appendix" accesskey="u" rel="up">Appendix</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Ecosystem" accesskey="n" rel="next">Ecosystem</a>, Up: <a href="#Appendix" accesskey="u" rel="up">Appendix</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Note_002dtaking-Workflows-1"></a>
 <h3 class="section">19.1 Note-taking Workflows</h3>
@@ -2137,7 +2093,7 @@ Next: <a href="#Ecosystem" accesskey="n" rel="next">Ecosystem</a>, Up: <a href="
 <a name="Ecosystem"></a>
 <div class="header">
 <p>
-Previous: <a href="#Note_002dtaking-Workflows" accesskey="p" rel="prev">Note-taking Workflows</a>, Up: <a href="#Appendix" accesskey="u" rel="up">Appendix</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Previous: <a href="#Note_002dtaking-Workflows" accesskey="p" rel="prev">Note-taking Workflows</a>, Up: <a href="#Appendix" accesskey="u" rel="up">Appendix</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Ecosystem-1"></a>
 <h3 class="section">19.2 Ecosystem</h3>
@@ -2159,14 +2115,19 @@ Previous: <a href="#Note_002dtaking-Workflows" accesskey="p" rel="prev">Note-tak
 <a name="Browsing-History-with-winner_002dmode"></a>
 <div class="header">
 <p>
-Next: <a href="#Versioning-Notes" accesskey="n" rel="next">Versioning Notes</a>, Up: <a href="#Ecosystem" accesskey="u" rel="up">Ecosystem</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Versioning-Notes" accesskey="n" rel="next">Versioning Notes</a>, Up: <a href="#Ecosystem" accesskey="u" rel="up">Ecosystem</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Browsing-History-with-winner_002dmode-1"></a>
 <h4 class="subsection">19.2.1 Browsing History with winner-mode</h4>
 
-<p><code>winner-mode</code> is a global minor mode that allows one to undo and redo changes in the window configuration. It is included with GNU Emacs since version 20.
+<p><code>winner-mode</code> is a global minor mode that allows one to undo and redo changes in
+the window configuration. It is included with GNU Emacs since version 20.
 </p>
-<p><code>winner-mode</code> can be used as a simple version of browser history for Org-roam. Each click through org-roam links (from both Org files and the backlinks buffer) causes changes in window configuration, which can be undone and redone using <code>winner-mode</code>. To use <code>winner-mode</code>, simply enable it, and bind the appropriate interactive functions:
+<p><code>winner-mode</code> can be used as a simple version of browser history for Org-roam.
+Each click through org-roam links (from both Org files and the backlinks buffer)
+causes changes in window configuration, which can be undone and redone using
+<code>winner-mode</code>. To use <code>winner-mode</code>, simply enable it, and bind the appropriate
+interactive functions:
 </p>
 <div class="lisp">
 <pre class="lisp">(winner-mode +1)
@@ -2179,7 +2140,7 @@ Next: <a href="#Versioning-Notes" accesskey="n" rel="next">Versioning Notes</a>,
 <a name="Versioning-Notes"></a>
 <div class="header">
 <p>
-Next: <a href="#Full_002dtext-search-interface-with-Deft" accesskey="n" rel="next">Full-text search interface with Deft</a>, Previous: <a href="#Browsing-History-with-winner_002dmode" accesskey="p" rel="prev">Browsing History with winner-mode</a>, Up: <a href="#Ecosystem" accesskey="u" rel="up">Ecosystem</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Full_002dtext-search-interface-with-Deft" accesskey="n" rel="next">Full-text search interface with Deft</a>, Previous: <a href="#Browsing-History-with-winner_002dmode" accesskey="p" rel="prev">Browsing History with winner-mode</a>, Up: <a href="#Ecosystem" accesskey="u" rel="up">Ecosystem</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Versioning-Notes-1"></a>
 <h4 class="subsection">19.2.2 Versioning Notes</h4>
@@ -2197,7 +2158,7 @@ versions of a tracked Org-roam note.
 <a name="Full_002dtext-search-interface-with-Deft"></a>
 <div class="header">
 <p>
-Next: <a href="#Org_002djournal" accesskey="n" rel="next">Org-journal</a>, Previous: <a href="#Versioning-Notes" accesskey="p" rel="prev">Versioning Notes</a>, Up: <a href="#Ecosystem" accesskey="u" rel="up">Ecosystem</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Org_002djournal" accesskey="n" rel="next">Org-journal</a>, Previous: <a href="#Versioning-Notes" accesskey="p" rel="prev">Versioning Notes</a>, Up: <a href="#Ecosystem" accesskey="u" rel="up">Ecosystem</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Full_002dtext-search-interface-with-Deft-1"></a>
 <h4 class="subsection">19.2.3 Full-text search interface with Deft</h4>
@@ -2216,10 +2177,9 @@ Next: <a href="#Org_002djournal" accesskey="n" rel="next">Org-journal</a>, Previ
   (deft-directory &quot;/path/to/org-roam-files/&quot;))
 </pre></div>
 
-<p>If the title of the Org file is not the first line, you might not get
-nice titles. You may choose to patch this to use <code>org-roam</code>&rsquo;s
-functionality. Here I&rsquo;m using
-<a href="https://github.com/raxod502/el-patch">el-patch</a>:
+<p>If the title of the Org file is not the first line, you might not get nice
+titles. You may choose to patch this to use <code>org-roam</code>&rsquo;s functionality. Here I&rsquo;m
+using <a href="https://github.com/raxod502/el-patch">el-patch</a>:
 </p>
 <div class="lisp">
 <pre class="lisp">(use-package el-patch
@@ -2247,24 +2207,22 @@ used as title.&quot;
                    (org-roam--get-title-or-slug file))))
 </pre></div>
 
-<p>The Deft interface can slow down quickly when the number of files get
-huge. <a href="https://github.com/hasu/notdeft">Notdeft</a> is a fork of Deft
-that uses an external search engine and indexer.
+<p>The Deft interface can slow down quickly when the number of files get huge.
+<a href="https://github.com/hasu/notdeft">Notdeft</a> is a fork of Deft that uses an external search engine and indexer.
 </p>
 <hr>
 <a name="Org_002djournal"></a>
 <div class="header">
 <p>
-Next: <a href="#Note_002dtaking-Add_002dons" accesskey="n" rel="next">Note-taking Add-ons</a>, Previous: <a href="#Full_002dtext-search-interface-with-Deft" accesskey="p" rel="prev">Full-text search interface with Deft</a>, Up: <a href="#Ecosystem" accesskey="u" rel="up">Ecosystem</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Note_002dtaking-Add_002dons" accesskey="n" rel="next">Note-taking Add-ons</a>, Previous: <a href="#Full_002dtext-search-interface-with-Deft" accesskey="p" rel="prev">Full-text search interface with Deft</a>, Up: <a href="#Ecosystem" accesskey="u" rel="up">Ecosystem</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Org_002djournal-1"></a>
 <h4 class="subsection">19.2.4 Org-journal</h4>
 
-<p><a href="https://github.com/bastibe/org-journal">Org-journal</a> provides journaling
-capabilities to Org-mode. A lot of its functionalities have been incorporated
-into Org-roam under the name <a href="#Daily_002dnotes"><code>org-roam-dailies</code></a>.  It remains
-a good tool if you want to isolate your verbose journal entries from the ideas
-you would write on a scratchpad.
+<p><a href="https://github.com/bastibe/org-journal">Org-journal</a> provides journaling capabilities to Org-mode. A lot of its
+functionalities have been incorporated into Org-roam under the name
+<a href="#Daily_002dnotes"><code>org-roam-dailies</code></a>. It remains a good tool if you want to isolate your verbose
+journal entries from the ideas you would write on a scratchpad.
 </p>
 <div class="lisp">
 <pre class="lisp">(use-package org-journal
@@ -2281,7 +2239,7 @@ you would write on a scratchpad.
 <a name="Note_002dtaking-Add_002dons"></a>
 <div class="header">
 <p>
-Previous: <a href="#Org_002djournal" accesskey="p" rel="prev">Org-journal</a>, Up: <a href="#Ecosystem" accesskey="u" rel="up">Ecosystem</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Previous: <a href="#Org_002djournal" accesskey="p" rel="prev">Org-journal</a>, Up: <a href="#Ecosystem" accesskey="u" rel="up">Ecosystem</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Note_002dtaking-Add_002dons-1"></a>
 <h4 class="subsection">19.2.5 Note-taking Add-ons</h4>
@@ -2305,7 +2263,7 @@ Previous: <a href="#Org_002djournal" accesskey="p" rel="prev">Org-journal</a>, U
 <a name="Org_002ddownload"></a>
 <div class="header">
 <p>
-Next: <a href="#mathpixel" accesskey="n" rel="next">mathpixel</a>, Up: <a href="#Note_002dtaking-Add_002dons" accesskey="u" rel="up">Note-taking Add-ons</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#mathpixel" accesskey="n" rel="next">mathpixel</a>, Up: <a href="#Note_002dtaking-Add_002dons" accesskey="u" rel="up">Note-taking Add-ons</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Org_002ddownload-1"></a>
 <h4 class="unnumberedsubsubsec">Org-download</h4>
@@ -2329,7 +2287,7 @@ Next: <a href="#mathpixel" accesskey="n" rel="next">mathpixel</a>, Up: <a href="
 <a name="mathpixel"></a>
 <div class="header">
 <p>
-Next: <a href="#Org_002dnoter-_002f-Interleave" accesskey="n" rel="next">Org-noter / Interleave</a>, Previous: <a href="#Org_002ddownload" accesskey="p" rel="prev">Org-download</a>, Up: <a href="#Note_002dtaking-Add_002dons" accesskey="u" rel="up">Note-taking Add-ons</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Org_002dnoter-_002f-Interleave" accesskey="n" rel="next">Org-noter / Interleave</a>, Previous: <a href="#Org_002ddownload" accesskey="p" rel="prev">Org-download</a>, Up: <a href="#Note_002dtaking-Add_002dons" accesskey="u" rel="up">Note-taking Add-ons</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="mathpix_002eel"></a>
 <h4 class="unnumberedsubsubsec">mathpix.el</h4>
@@ -2353,7 +2311,7 @@ Next: <a href="#Org_002dnoter-_002f-Interleave" accesskey="n" rel="next">Org-not
 <a name="Org_002dnoter-_002f-Interleave"></a>
 <div class="header">
 <p>
-Next: <a href="#Bibliography" accesskey="n" rel="next">Bibliography</a>, Previous: <a href="#mathpixel" accesskey="p" rel="prev">mathpixel</a>, Up: <a href="#Note_002dtaking-Add_002dons" accesskey="u" rel="up">Note-taking Add-ons</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Bibliography" accesskey="n" rel="next">Bibliography</a>, Previous: <a href="#mathpixel" accesskey="p" rel="prev">mathpixel</a>, Up: <a href="#Note_002dtaking-Add_002dons" accesskey="u" rel="up">Note-taking Add-ons</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Org_002dnoter-_002f-Interleave-1"></a>
 <h4 class="unnumberedsubsubsec">Org-noter / Interleave</h4>
@@ -2367,7 +2325,7 @@ etc.) within Org-mode.
 <a name="Bibliography"></a>
 <div class="header">
 <p>
-Next: <a href="#Spaced-Repetition" accesskey="n" rel="next">Spaced Repetition</a>, Previous: <a href="#Org_002dnoter-_002f-Interleave" accesskey="p" rel="prev">Org-noter / Interleave</a>, Up: <a href="#Note_002dtaking-Add_002dons" accesskey="u" rel="up">Note-taking Add-ons</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Spaced-Repetition" accesskey="n" rel="next">Spaced Repetition</a>, Previous: <a href="#Org_002dnoter-_002f-Interleave" accesskey="p" rel="prev">Org-noter / Interleave</a>, Up: <a href="#Note_002dtaking-Add_002dons" accesskey="u" rel="up">Note-taking Add-ons</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Bibliography-1"></a>
 <h4 class="unnumberedsubsubsec">Bibliography</h4>
@@ -2379,13 +2337,15 @@ tight integration between
 <code>org-roam</code>. This helps you manage your bibliographic notes under
 <code>org-roam</code>.
 </p>
-<p>For example, though helm-bibtex provides the ability to visit notes for bibliographic entries, org-roam-bibtex extends it with the ability to visit the file with the right &lsquo;<samp>#+roam_key</samp>&rsquo;.
+<p>For example, though helm-bibtex provides the ability to visit notes for
+bibliographic entries, org-roam-bibtex extends it with the ability to visit the
+file with the right &lsquo;<samp>#+roam_key</samp>&rsquo;.
 </p>
 <hr>
 <a name="Spaced-Repetition"></a>
 <div class="header">
 <p>
-Previous: <a href="#Bibliography" accesskey="p" rel="prev">Bibliography</a>, Up: <a href="#Note_002dtaking-Add_002dons" accesskey="u" rel="up">Note-taking Add-ons</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Previous: <a href="#Bibliography" accesskey="p" rel="prev">Bibliography</a>, Up: <a href="#Note_002dtaking-Add_002dons" accesskey="u" rel="up">Note-taking Add-ons</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Spaced-Repetition-1"></a>
 <h4 class="unnumberedsubsubsec">Spaced Repetition</h4>
@@ -2397,7 +2357,7 @@ files. Other alternatives include <a href="https://orgmode.org/worg/org-contrib/
 <a name="FAQ"></a>
 <div class="header">
 <p>
-Next: <a href="#Keystroke-Index" accesskey="n" rel="next">Keystroke Index</a>, Previous: <a href="#Appendix" accesskey="p" rel="prev">Appendix</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Keystroke-Index" accesskey="n" rel="next">Keystroke Index</a>, Previous: <a href="#Appendix" accesskey="p" rel="prev">Appendix</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="FAQ-1"></a>
 <h2 class="chapter">20 FAQ</h2>
@@ -2415,7 +2375,7 @@ Next: <a href="#Keystroke-Index" accesskey="n" rel="next">Keystroke Index</a>, P
 <a name="How-do-I-have-more-than-one-Org_002droam-directory_003f"></a>
 <div class="header">
 <p>
-Next: <a href="#How-do-I-migrate-from-Roam-Research_003f" accesskey="n" rel="next">How do I migrate from Roam Research?</a>, Up: <a href="#FAQ" accesskey="u" rel="up">FAQ</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#How-do-I-migrate-from-Roam-Research_003f" accesskey="n" rel="next">How do I migrate from Roam Research?</a>, Up: <a href="#FAQ" accesskey="u" rel="up">FAQ</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="How-do-I-have-more-than-one-Org_002droam-directory_003f-1"></a>
 <h3 class="section">20.1 How do I have more than one Org-roam directory?</h3>
@@ -2433,26 +2393,28 @@ contain:
          (org-roam-db-location . &quot;./org-roam.db&quot;))))
 </pre></div>
 
-<p>All files within that directory will be treated as their own separate
-set of Org-roam files. Remember to run <code>org-roam-db-build-cache</code> from a
-file within that directory, at least once.
+<p>All files within that directory will be treated as their own separate set of
+Org-roam files. Remember to run <code>org-roam-db-build-cache</code> from a file within
+that directory, at least once.
 </p>
 <hr>
 <a name="How-do-I-migrate-from-Roam-Research_003f"></a>
 <div class="header">
 <p>
-Next: <a href="#How-do-I-create-a-note-whose-title-already-matches-one-of-the-candidates_003f" accesskey="n" rel="next">How do I create a note whose title already matches one of the candidates?</a>, Previous: <a href="#How-do-I-have-more-than-one-Org_002droam-directory_003f" accesskey="p" rel="prev">How do I have more than one Org-roam directory?</a>, Up: <a href="#FAQ" accesskey="u" rel="up">FAQ</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#How-do-I-create-a-note-whose-title-already-matches-one-of-the-candidates_003f" accesskey="n" rel="next">How do I create a note whose title already matches one of the candidates?</a>, Previous: <a href="#How-do-I-have-more-than-one-Org_002droam-directory_003f" accesskey="p" rel="prev">How do I have more than one Org-roam directory?</a>, Up: <a href="#FAQ" accesskey="u" rel="up">FAQ</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="How-do-I-migrate-from-Roam-Research_003f-1"></a>
 <h3 class="section">20.2 How do I migrate from Roam Research?</h3>
 
-<p>Fabio has produced a command-line tool that converts markdown files exported from Roam Research into Org-roam compatible markdown. More instructions are provided <a href="https://github.com/fabioberger/roam-migration">in the repository</a>.
+<p>Fabio has produced a command-line tool that converts markdown files exported
+from Roam Research into Org-roam compatible markdown. More instructions are
+provided <a href="https://github.com/fabioberger/roam-migration">in the repository</a>.
 </p>
 <hr>
 <a name="How-do-I-create-a-note-whose-title-already-matches-one-of-the-candidates_003f"></a>
 <div class="header">
 <p>
-Previous: <a href="#How-do-I-migrate-from-Roam-Research_003f" accesskey="p" rel="prev">How do I migrate from Roam Research?</a>, Up: <a href="#FAQ" accesskey="u" rel="up">FAQ</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Previous: <a href="#How-do-I-migrate-from-Roam-Research_003f" accesskey="p" rel="prev">How do I migrate from Roam Research?</a>, Up: <a href="#FAQ" accesskey="u" rel="up">FAQ</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="How-do-I-create-a-note-whose-title-already-matches-one-of-the-candidates_003f-1"></a>
 <h3 class="section">20.3 How do I create a note whose title already matches one of the candidates?</h3>
@@ -2464,16 +2426,18 @@ Previous: <a href="#How-do-I-migrate-from-Roam-Research_003f" accesskey="p" rel=
 are the solutions:
 </p>
 <ul>
-<li> Ivycall <code>ivy-immediate-done</code>, typically bound to <code>C-M-j</code>. Alternatively, set <code>ivy-use-selectable-prompt</code> to <code>t</code>, so that &ldquo;bar&rdquo; is now selectable.
+<li> Ivycall <code>ivy-immediate-done</code>, typically bound to <code>C-M-j</code>. Alternatively,
+set <code>ivy-use-selectable-prompt</code> to <code>t</code>, so that &ldquo;bar&rdquo; is now selectable.
 
-</li><li> HelmOrg-roam should provide a selectable &ldquo;[?] bar&rdquo; candidate at the top of the candidate list.
+</li><li> HelmOrg-roam should provide a selectable &ldquo;[?] bar&rdquo; candidate at the top of
+the candidate list.
 </li></ul>
 
 <hr>
 <a name="Keystroke-Index"></a>
 <div class="header">
 <p>
-Next: <a href="#Command-Index" accesskey="n" rel="next">Command Index</a>, Previous: <a href="#FAQ" accesskey="p" rel="prev">FAQ</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Command-Index" accesskey="n" rel="next">Command Index</a>, Previous: <a href="#FAQ" accesskey="p" rel="prev">FAQ</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Keystroke-Index-1"></a>
 <h2 class="appendix">Appendix A Keystroke Index</h2>
@@ -2483,7 +2447,7 @@ Next: <a href="#Command-Index" accesskey="n" rel="next">Command Index</a>, Previ
 <a name="Command-Index"></a>
 <div class="header">
 <p>
-Next: <a href="#Function-Index" accesskey="n" rel="next">Function Index</a>, Previous: <a href="#Keystroke-Index" accesskey="p" rel="prev">Keystroke Index</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Function-Index" accesskey="n" rel="next">Function Index</a>, Previous: <a href="#Keystroke-Index" accesskey="p" rel="prev">Keystroke Index</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Command-Index-1"></a>
 <h2 class="appendix">Appendix B Command Index</h2>
@@ -2493,7 +2457,7 @@ Next: <a href="#Function-Index" accesskey="n" rel="next">Function Index</a>, Pre
 <a name="Function-Index"></a>
 <div class="header">
 <p>
-Next: <a href="#Variable-Index" accesskey="n" rel="next">Variable Index</a>, Previous: <a href="#Command-Index" accesskey="p" rel="prev">Command Index</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="#Variable-Index" accesskey="n" rel="next">Variable Index</a>, Previous: <a href="#Command-Index" accesskey="p" rel="prev">Command Index</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Function-Index-1"></a>
 <h2 class="appendix">Appendix C Function Index</h2>
@@ -2527,7 +2491,7 @@ Next: <a href="#Variable-Index" accesskey="n" rel="next">Variable Index</a>, Pre
 <a name="Variable-Index"></a>
 <div class="header">
 <p>
-Previous: <a href="#Function-Index" accesskey="p" rel="prev">Function Index</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
+Previous: <a href="#Function-Index" accesskey="p" rel="prev">Function Index</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Keystroke-Index" title="Index" rel="index">Index</a>]</p>
 </div>
 <a name="Variable-Index-1"></a>
 <h2 class="appendix">Appendix D Variable Index</h2>
diff --git a/org-roam.org b/org-roam.org
index 710f582..6e0e3fb 100644
--- a/org-roam.org
+++ b/org-roam.org
@@ -1,22 +1,19 @@
 #+title: Org-roam User Manual
-:PREAMBLE:
 #+author: Jethro Kuan
 #+email: jethrokuan95@gmail.com
 #+date: 2020-2020
 #+language: en
 
-
 #+texinfo_deffn: t
 #+texinfo_dir_category: Emacs
 #+texinfo_dir_title: Org-roam: (org-roam).
 #+texinfo_dir_desc: Rudimentary Roam Replica for Emacs.
 #+subtitle: for version 1.2.2
 
-#+options: H:4 num:3 toc:2 creator:t ':t
+#+options: H:4 num:3 toc:nil creator:t ':t
 #+property: header-args :eval never
 #+texinfo: @noindent
 
-#+texinfo: @noindent
 This manual is for Org-roam version 1.2.2.
 
 #+BEGIN_QUOTE
@@ -32,8 +29,6 @@ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
 General Public License for more details.
 #+END_QUOTE
 
-:END:
-
 * Introduction
 
 Org-roam is a [[https://roamresearch.com/][Roam Research]] replica built around the
@@ -53,11 +48,23 @@ to further introduce features enabled by the Emacs ecosystem.
 
 Org-roam provides several benefits over other tooling:
 
-- Privacy and Security :: Edit your personal wiki completely offline, entirely in your control. Encrypt your notes with GPG.
-- Longevity of Plain Text :: Unlike web solutions like Roam research, the notes are first and foremost plain Org-mode files -- Org-roam simply builds up an auxilliary database to give the personal wiki superpowers. Having your notes in plain-text is crucial for the longevity of your wiki. Never have to worry about proprietary web solutions being taken down. Edit your plain-text notes in notepad if all other editors cease to exist
-- Free and Open Source :: Org-roam is free and open-source, which means that if you feel unhappy with any part of Org-roam, you may choose to extend Org-roam, or open a PR.
-- Leverages the Org-mode ecosystem :: Over the years, Emacs and Org-mode has developed into a mature system for plain-text organization. Building upon Org-mode already puts Org-roam light-years ahead of many other solutions.
-- Built on Emacs :: Emacs is also a fantastic interface for editing text, and we can inherit many of the powerful text-navigation and editing packages available to Emacs.
+- Privacy and Security :: Edit your personal wiki completely offline, entirely
+  in your control. Encrypt your notes with GPG.
+- Longevity of Plain Text :: Unlike web solutions like Roam research, the notes
+  are first and foremost plain Org-mode files -- Org-roam simply builds up an
+  auxilliary database to give the personal wiki superpowers. Having your notes
+  in plain-text is crucial for the longevity of your wiki. Never have to worry
+  about proprietary web solutions being taken down. Edit your plain-text notes
+  in notepad if all other editors cease to exist
+- Free and Open Source :: Org-roam is free and open-source, which means that if
+  you feel unhappy with any part of Org-roam, you may choose to extend Org-roam,
+  or open a PR.
+- Leverages the Org-mode ecosystem :: Over the years, Emacs and Org-mode has
+  developed into a mature system for plain-text organization. Building upon
+  Org-mode already puts Org-roam light-years ahead of many other solutions.
+- Built on Emacs :: Emacs is also a fantastic interface for editing text, and we
+  can inherit many of the powerful text-navigation and editing packages
+  available to Emacs.
 
 * Target Audience
 
@@ -204,9 +211,16 @@ Org-roam will then be autoloaded into Emacs.
 
 ** Installing from the Git Repository
 
-You may install Org-roam directly from the repository on [[https://github.com/org-roam/org-roam][GitHub]] if you like. This will give you access to the latest version hours or days before it appears on MELPA, and months (or more) before it is added to the Debian or Ubuntu repositories. This will also give you access to various developmental branches that may be available. 
+You may install Org-roam directly from the repository on [[https://github.com/org-roam/org-roam][GitHub]] if you like.
+This will give you access to the latest version hours or days before it appears
+on MELPA, and months (or more) before it is added to the Debian or Ubuntu
+repositories. This will also give you access to various developmental branches
+that may be available.
 
-Note, however, that development version, and especially any feature branches, may not always be in working order. You'll need to be prepared to do some debugging, or to manually roll-back to working versions, if you install from GitHub.
+Note, however, that development version, and especially any feature branches,
+may not always be in working order. You'll need to be prepared to do some
+debugging, or to manually roll-back to working versions, if you install from
+GitHub.
 
 Installing from GitHub requires that you clone the repository:
 
@@ -216,14 +230,16 @@ git clone https://github.com/org-roam/org-roam.git /path/to/org/roam
 
 where ~./path/to/org/roam~ is the location you will store your copy of the code.
 
-Next, you need to add this location to your load path, and ~require~ the Org-roam library. Add the following code to your ~.emacs~:
+Next, you need to add this location to your load path, and ~require~ the
+Org-roam library. Add the following code to your ~.emacs~:
 
 #+begin_src elisp
 (add-to-list 'load-path "/path/to/org/roam")
 (require 'org-roam)
 #+end_src
 
-You now have Org-roam installed. However, you don't necessarily have the dependencies that it requires. These include:
+You now have Org-roam installed. However, you don't necessarily have the
+dependencies that it requires. These include:
 
 - dash
 - f
@@ -232,17 +248,25 @@ You now have Org-roam installed. However, you don't necessarily have the depende
 - emacsql
 - emacsql-sqlite3
 
-You can install this manually as well, or get the latest version from MELPA. You may wish to use [[https://github.com/jwiegley/use-package][use-package]], [[https://github.com/raxod502/straight.el][straight.el]], or some other tool or tools to help manage this.
+You can install this manually as well, or get the latest version from MELPA. You
+may wish to use [[https://github.com/jwiegley/use-package][use-package]], [[https://github.com/raxod502/straight.el][straight.el]], or some other tool or tools to help
+manage this.
 
-If you would like to install the manual for access from Emacs' built-in Info system, you'll need to compile the .texi source file, and install it in an appropriate location.
+If you would like to install the manual for access from Emacs' built-in Info
+system, you'll need to compile the .texi source file, and install it in an
+appropriate location.
 
-To compile the .texi source file, from a terminal navigate to the ~/doc~ subdirectory of the Org-roam repository, and run the following:
+To compile the .texi source file, from a terminal navigate to the ~/doc~
+subdirectory of the Org-roam repository, and run the following:
 
 #+begin_src bash
 make infodir=/path/to/my/info/files install-info
 #+end_src
 
-Where ~/path/to/my/info/files~ is the location where you keep info files. This target directory needs to be stored in the variable `Info-default-directory-list`. If you aren't using one of the default info locations, you can configure this with the following in your ~.emacs~ file:
+Where ~/path/to/my/info/files~ is the location where you keep info files. This
+target directory needs to be stored in the variable
+`Info-default-directory-list`. If you aren't using one of the default info
+locations, you can configure this with the following in your ~.emacs~ file:
 
 #+begin_src elisp
   (require 'info)
@@ -256,9 +280,11 @@ You can also use one of the default locations, such as:
 - /usr/share/info/
 - /usr/local/share/info/
 
-If you do this, you'll need to make sure you have write-access to that location, or run the above ~make~ command as root.
+If you do this, you'll need to make sure you have write-access to that location,
+or run the above ~make~ command as root.
 
-Now that the info file is ready, you need to add it to the corresponding ~dir~ file:
+Now that the info file is ready, you need to add it to the corresponding ~dir~
+file:
 
 #+begin_src bash
 install-info /path/to/my/info/files/org-roam.info /path/to/my/info/files/dir
@@ -405,13 +431,15 @@ If you wish to add your own title extraction method, you may push a symbol
 
 Tags are used as meta-data for files: they facilitate interactions with notes
 where titles are insufficient. For example, tags allow for categorization of
-notes: differentiating between bibliographical and structure notes during interactive commands.
+notes: differentiating between bibliographical and structure notes during
+interactive commands.
 
 Org-roam calls ~org-roam--extract-tags~ to extract tags from files. It uses the
 variable ~org-roam-tag-sources~, to control how tags are extracted. The tag
 extraction methods supported are:
 
-1. ~'prop~: This extracts tags from the ~#+roam_tags~ property. Tags are space delimited, and can be multi-word using double quotes.
+1. ~'prop~: This extracts tags from the ~#+roam_tags~ property. Tags are space
+   delimited, and can be multi-word using double quotes.
 2. ~'all-directories~: All sub-directories relative to ~org-roam-directory~ are
    extracted as tags. That is, if a file is located at relative path
    ~foo/bar/file.org~, the file will have tags ~foo~ and ~bar~.
@@ -436,19 +464,20 @@ accepts the absolute file path as its argument. See
 
 ** File Refs
 
-Refs are unique identifiers for files. For example, a note for a website may contain a ref:
+Refs are unique identifiers for files. For example, a note for a website may
+contain a ref:
 
 #+BEGIN_SRC org
   #+title: Google
   #+roam_key: https://www.google.com/
 #+END_SRC
 
-These keys allow references to the key to show up in the backlinks buffer. For instance,
-with the example above, if another file then links to https://www.google.com, that will
-show up as a “Ref Backlink”.
+These keys allow references to the key to show up in the backlinks buffer. For
+instance, with the example above, if another file then links to
+https://www.google.com, that will show up as a “Ref Backlink”.
 
-These keys also come in useful for when taking website notes, using the ~roam-ref~ protocol
- (see [[*Roam Protocol][Roam Protocol]]).
+These keys also come in useful for when taking website notes, using the
+ ~roam-ref~ protocol (see [[*Roam Protocol][Roam Protocol]]).
 
 [[https://github.com/jkitchin/org-ref][org-ref]] citation keys can also be used as refs:
 
@@ -460,9 +489,9 @@ These keys also come in useful for when taking website notes, using the ~roam-re
 #+CAPTION: org-ref-citelink
 [[file:images/org-ref-citelink.png]]
 
-You may assign multiple refs to a single file, for example when you want multiple papers
-in a series to share the same note, or an article has a citation key and a URL at the same
-time.
+You may assign multiple refs to a single file, for example when you want
+multiple papers in a series to share the same note, or an article has a citation
+key and a URL at the same time.
 * The Templating System
 
 Rather than creating blank files on ~org-roam-insert~ and ~org-roam-find-file~,
@@ -500,15 +529,14 @@ the default template, reproduced below.
        :unnarrowed t)
 #+END_SRC
 
-1. The template has short key ~"d"~. If you have only one template,
-   org-roam automatically chooses this template for you.
+1. The template has short key ~"d"~. If you have only one template, org-roam
+   automatically chooses this template for you.
 2. The template is given a description of ~"default"~.
 3. ~plain~ text is inserted. Other options include Org headings via
    ~entry~.
 4. ~(function org-roam--capture-get-point)~ should not be changed.
 5. ~"%?"~ is the template inserted on each call to ~org-roam-capture--capture~.
-   This template means don't insert any content, but place the cursor
-   here.
+   This template means don't insert any content, but place the cursor here.
 6. ~:file-name~ is the file-name template for a new note, if it doesn't yet
    exist. This creates a file at path that looks like
    ~/path/to/org-roam-directory/20200213032037-foo.org~. This template also
@@ -537,9 +565,9 @@ provided title. ~${title}~ is then expanded into the provided title during the
 org-capture process. Any variables that do not contain strings, are prompted for
 values using ~completing-read~.
 
-After doing this expansion, the org-capture's template expansion system
-is used to fill up the rest of the template. You may read up more on
-this on [[https://orgmode.org/manual/Template-expansion.html#Template-expansion][org-capture's documentation page]].
+After doing this expansion, the org-capture's template expansion system is used
+to fill up the rest of the template. You may read up more on this on
+[[https://orgmode.org/manual/Template-expansion.html#Template-expansion][org-capture's documentation page]].
 
 To illustrate this dual expansion process, take for example the template string:
 ~"%<%Y%m%d%H%M%S>-${title}"~, with the title ~"Foo"~. The template is first
@@ -560,12 +588,12 @@ directly to provide its third argument to specify UTC.
 #+END_SRC
 
 * Concepts and Configuration
-The number of configuration options is deliberately kept small, to keep
-the Org-roam codebase manageable. However, we attempt to accommodate as
-many usage styles as possible.
+The number of configuration options is deliberately kept small, to keep the
+Org-roam codebase manageable. However, we attempt to accommodate as many usage
+styles as possible.
 
-All of Org-roam's customization options can be viewed via
-~M-x customize-group org-roam~.
+All of Org-roam's customization options can be viewed via ~M-x customize-group
+org-roam~.
 
 ** Directories and Files
 
@@ -661,14 +689,17 @@ An alternative mode of insertion is using Org-roam's ~roam~ links. Org-roam
 registers this link type, and interprets the path as follows:
 
 - ~[[roam:title]]~ :: links to an Org-roam file with title or alias "title"
-- ~[[roam:*headline]]~ :: links to the headline "headline" in the current Org-roam file
-- ~[[roam:title*headline]]~ :: links to the headline "headline" in the Org-roam file with title or alias "title"
+- ~[[roam:*headline]]~ :: links to the headline "headline" in the current
+  Org-roam file
+- ~[[roam:title*headline]]~ :: links to the headline "headline" in the Org-roam
+  file with title or alias "title"
 
 ~roam~ links support auto-completion via ~completion-at-point~: simply call
 ~completion-at-point~ within a roam link. Users of ~company-mode~ may want to
 prepend ~company-capf~ to the beginning of variable ~company-backends~.
 
-To easily insert ~roam~ links, one may wish to use a package like [[https://github.com/emacsorphanage/key-chord/][key-chord]]. In the following example, typing "[[" will insert a stub ~roam~ link:
+To easily insert ~roam~ links, one may wish to use a package like [[https://github.com/emacsorphanage/key-chord/][key-chord]]. In
+the following example, typing "[[" will insert a stub ~roam~ link:
 
 #+BEGIN_SRC emacs-lisp
 (key-chord-define org-mode-map "[[" #'my/insert-roam-link)
@@ -731,13 +762,14 @@ GPG), which can be enabled for all new files by setting ~org-roam-encrypt-files~
 to ~t~. When enabled, new files are created with the ~.org.gpg~ extension and
 decryption are handled automatically by EasyPG.
 
-Note that Emacs will prompt for a password for encrypted files during
-cache updates if it requires reading the encrypted file. To reduce the
-number of password prompts, you may wish to cache the password.
+Note that Emacs will prompt for a password for encrypted files during cache
+updates if it requires reading the encrypted file. To reduce the number of
+password prompts, you may wish to cache the password.
 
 - User Option: org-roam-encrypt-files
 
-  Whether to encrypt new files.  If true, create files with .org.gpg extension.
+  Whether to encrypt new files. If true, create files with .org.gpg extension.
+
 * Graphing
 
 Org-roam provides graphing capabilities to explore interconnections between
@@ -761,21 +793,24 @@ The entry point to graph creation is ~org-roam-graph~.
 
 - User Option: org-roam-graph-executable
 
-  Path to the graphing executable (in this case, Graphviz). Set this if Org-roam is unable to find the Graphviz executable on your system.
+  Path to the graphing executable (in this case, Graphviz). Set this if Org-roam
+  is unable to find the Graphviz executable on your system.
 
   You may also choose to use ~neato~ in place of ~dot~, which generates a more
   compact graph layout.
 
 - User Option: org-roam-graph-viewer
 
-  Org-roam defaults to using Firefox (located on PATH) to view the SVG, but you may choose to set it to:
+  Org-roam defaults to using Firefox (located on PATH) to view the SVG, but you
+  may choose to set it to:
 
   1. A string, which is a path to the program used
   2. a function accepting a single argument: the graph file path.
 
   ~nil~ uses ~view-file~ to view the graph.
   
-  If you are using WSL2 and would like to open the graph in Windows, you can use the second option to set the browser and network file path:
+  If you are using WSL2 and would like to open the graph in Windows, you can use
+  the second option to set the browser and network file path:
   
   #+BEGIN_SRC emacs-lisp
   (setq org-roam-graph-viewer
@@ -786,7 +821,9 @@ The entry point to graph creation is ~org-roam-graph~.
 
 ** Graph Options
 
-Graphviz provides many options for customizing the graph output, and Org-roam supports some of them. See https://graphviz.gitlab.io/_pages/doc/info/attrs.html for customizable options.
+Graphviz provides many options for customizing the graph output, and Org-roam
+supports some of them. See https://graphviz.gitlab.io/_pages/doc/info/attrs.html
+for customizable options.
 
 - User Option: org-roam-graph-extra-config
 
@@ -852,12 +889,13 @@ Other options include ~'ido~, and ~'ivy~.
 
 * Roam Protocol
 
-Org-roam extends ~org-protocol~ with 2 protocols: the ~roam-file~
-and ~roam-ref~ protocols.
+Org-roam extends ~org-protocol~ with 2 protocols: the ~roam-file~ and ~roam-ref~
+protocols.
 
 ** Installation
 
-To enable Org-roam's protocol extensions, you have to add the following to your init file:
+To enable Org-roam's protocol extensions, you have to add the following to your
+init file:
 
 #+BEGIN_SRC emacs-lisp
 (require 'org-roam-protocol)
@@ -868,7 +906,8 @@ The instructions for setting up ~org-protocol~ are reproduced below.
 We will also need to create a desktop application for ~emacsclient~. The
 instructions for various platforms are shown below.
 
-For Linux users, create a desktop application in ~~/.local/share/applications/org-protocol.desktop~:
+For Linux users, create a desktop application in
+~~/.local/share/applications/org-protocol.desktop~:
 
 #+begin_example
 [Desktop Entry]
@@ -887,9 +926,9 @@ running in your shell:
 xdg-mime default org-protocol.desktop x-scheme-handler/org-protocol
 #+END_SRC
 
-To disable the "confirm" prompt in Chrome, you can also make Chrome
-show a checkbox to tick, so that the ~Org-Protocol Client~ app will be used
-without confirmation. To do this, run in a shell:
+To disable the "confirm" prompt in Chrome, you can also make Chrome show a
+checkbox to tick, so that the ~Org-Protocol Client~ app will be used without
+confirmation. To do this, run in a shell:
 
 #+BEGIN_SRC bash
 sudo mkdir -p /etc/opt/chrome/policies/managed/
@@ -981,13 +1020,15 @@ REGEDIT4
 @="\"C:\\Windows\\System32\\wsl.exe\" emacsclient \"%1\""
 #+END_SRC
 
-The above will forward the protocol to WSL. If you run Emacs natively on Windows, replace the last line with:
+The above will forward the protocol to WSL. If you run Emacs natively on
+Windows, replace the last line with:
 
 #+BEGIN_SRC text
 @="\"c:\\path\\to\\emacs\\bin\\emacsclientw.exe\"  \"%1\""
 #+END_SRC
 
-After executing the .reg file, the protocol is registered and you can delete the file.
+After executing the .reg file, the protocol is registered and you can delete the
+file.
 
 ** The roam-file protocol
 
@@ -1055,8 +1096,8 @@ Here is a sane default configuration:
 #+end_src
 
 Make sure that ~org-roam-dailies-directory~ appears in ~:file-name~ for your
-notes to be recognized as daily-notes. You can have different templates
-placing their notes in different directories, but the one in
+notes to be recognized as daily-notes. You can have different templates placing
+their notes in different directories, but the one in
 ~org-roam-dailies-directory~ will be considered as the main one in commands.
 
 See [[*The Templating System][The Templating System]] for creating new
@@ -1081,7 +1122,7 @@ specifying the outline-path to a heading:
 #+end_src
 
 The template ~l~ will put its notes under the heading ‘Lab notes’, and the
-template ~j~ will put its notes under the heading ‘Journal’.  When you use
+template ~j~ will put its notes under the heading ‘Journal’. When you use
 ~:olp~, make sure that the headings are present in ~:head~.
 
 ** Capturing and finding daily-notes
@@ -1153,10 +1194,11 @@ org-roam-doctor~, but note that this may take some time.
   Perform a check on Org-roam files to ensure cleanliness. If THIS-BUFFER, run
   the check only for the current buffer.
 
-The checks run are defined in ~org-roam-doctor--checkers~. By default, there are checkers for broken links and invalid =#+roam_*= properties.
+The checks run are defined in ~org-roam-doctor--checkers~. By default, there are
+checkers for broken links and invalid =#+roam_*= properties.
 
-Each checker is an instance of ~org-roam-doctor-checker~. To define a checker, use
-~make-org-roam-doctor-checker~. Here is a sample definition:
+Each checker is an instance of ~org-roam-doctor-checker~. To define a checker,
+use ~make-org-roam-doctor-checker~. Here is a sample definition:
 
 #+BEGIN_SRC emacs-lisp
 (make-org-roam-doctor-checker
@@ -1168,10 +1210,10 @@ Each checker is an instance of ~org-roam-doctor-checker~. To define a checker, u
 #+END_SRC
 
 The ~:name~ property is the name of the function run. The function takes in the
-Org parse tree, and returns a list of ~(point error-message)~. ~:description~ is a
-short description of what the checker does. ~:actions~ is an alist containing
-elements of the form ~(char . (prompt . function))~. These actions are defined per
-checker, to perform autofixes for the errors. For each error detected,
+Org parse tree, and returns a list of ~(point error-message)~. ~:description~ is
+a short description of what the checker does. ~:actions~ is an alist containing
+elements of the form ~(char . (prompt . function))~. These actions are defined
+per checker, to perform autofixes for the errors. For each error detected,
 ~org-roam-doctor~ will move the point to the current error, and pop-up a help
 window displaying the error message, as well as the list of actions that can be
 taken provided in ~:actions~.
@@ -1199,7 +1241,9 @@ unlinked references within encrypted files.
 ** Garbage Collection
 
 During the cache-build process, Org-roam generates a lot of in-memory
-data-structures (such as the Org file's AST), which are discarded after use. These structures are garbage collected at regular intervals (see [[info:elisp#Garbage Collection][info:elisp#Garbage Collection]]).
+data-structures (such as the Org file's AST), which are discarded after use.
+These structures are garbage collected at regular intervals (see [[info:elisp#Garbage
+ Collection][info:elisp#Garbage Collection]]).
 
 Org-roam provides the option ~org-roam-db-gc-threshold~ to temporarily change
 the threshold value for GC to be triggered during these memory-intensive
@@ -1247,9 +1291,14 @@ General Public License for more details.
 
 *** Browsing History with winner-mode
 
-~winner-mode~ is a global minor mode that allows one to undo and redo changes in the window configuration. It is included with GNU Emacs since version 20.
+~winner-mode~ is a global minor mode that allows one to undo and redo changes in
+the window configuration. It is included with GNU Emacs since version 20.
 
-~winner-mode~ can be used as a simple version of browser history for Org-roam. Each click through org-roam links (from both Org files and the backlinks buffer) causes changes in window configuration, which can be undone and redone using ~winner-mode~. To use ~winner-mode~, simply enable it, and bind the appropriate interactive functions:
+~winner-mode~ can be used as a simple version of browser history for Org-roam.
+Each click through org-roam links (from both Org files and the backlinks buffer)
+causes changes in window configuration, which can be undone and redone using
+~winner-mode~. To use ~winner-mode~, simply enable it, and bind the appropriate
+interactive functions:
 
 #+BEGIN_SRC emacs-lisp
   (winner-mode +1)
@@ -1287,10 +1336,9 @@ versions of a tracked Org-roam note.
     (deft-directory "/path/to/org-roam-files/"))
 #+END_SRC
 
-If the title of the Org file is not the first line, you might not get
-nice titles. You may choose to patch this to use ~org-roam~'s
-functionality. Here I'm using
-[[https://github.com/raxod502/el-patch][el-patch]]:
+If the title of the Org file is not the first line, you might not get nice
+titles. You may choose to patch this to use ~org-roam~'s functionality. Here I'm
+using [[https://github.com/raxod502/el-patch][el-patch]]:
 
 #+BEGIN_SRC emacs-lisp
   (use-package el-patch
@@ -1318,20 +1366,18 @@ functionality. Here I'm using
                      (org-roam--get-title-or-slug file))))
 #+END_SRC
 
-The Deft interface can slow down quickly when the number of files get
-huge. [[https://github.com/hasu/notdeft][Notdeft]] is a fork of Deft
-that uses an external search engine and indexer.
+The Deft interface can slow down quickly when the number of files get huge.
+[[https://github.com/hasu/notdeft][Notdeft]] is a fork of Deft that uses an external search engine and indexer.
 
 *** Org-journal
    :PROPERTIES:
    :CUSTOM_ID: org-journal
    :END:
 
-[[https://github.com/bastibe/org-journal][Org-journal]] provides journaling
-capabilities to Org-mode. A lot of its functionalities have been incorporated
-into Org-roam under the name [[*Daily-notes][~org-roam-dailies~]].  It remains
-a good tool if you want to isolate your verbose journal entries from the ideas
-you would write on a scratchpad.
+[[https://github.com/bastibe/org-journal][Org-journal]] provides journaling capabilities to Org-mode. A lot of its
+functionalities have been incorporated into Org-roam under the name
+[[*Daily-notes][~org-roam-dailies~]]. It remains a good tool if you want to isolate your verbose
+journal entries from the ideas you would write on a scratchpad.
 
 #+BEGIN_SRC emacs-lisp
   (use-package org-journal
@@ -1411,7 +1457,9 @@ tight integration between
 ~org-roam~. This helps you manage your bibliographic notes under
 ~org-roam~.
 
-For example, though helm-bibtex provides the ability to visit notes for bibliographic entries, org-roam-bibtex extends it with the ability to visit the file with the right =#+roam_key=.
+For example, though helm-bibtex provides the ability to visit notes for
+bibliographic entries, org-roam-bibtex extends it with the ability to visit the
+file with the right =#+roam_key=.
 
 **** Spaced Repetition
     :PROPERTIES:
@@ -1437,13 +1485,15 @@ contain:
              (org-roam-db-location . "./org-roam.db"))))
 #+END_SRC
 
-All files within that directory will be treated as their own separate
-set of Org-roam files. Remember to run ~org-roam-db-build-cache~ from a
-file within that directory, at least once.
+All files within that directory will be treated as their own separate set of
+Org-roam files. Remember to run ~org-roam-db-build-cache~ from a file within
+that directory, at least once.
 
 ** How do I migrate from Roam Research?
 
-Fabio has produced a command-line tool that converts markdown files exported from Roam Research into Org-roam compatible markdown. More instructions are provided [[https://github.com/fabioberger/roam-migration][in the repository]].
+Fabio has produced a command-line tool that converts markdown files exported
+from Roam Research into Org-roam compatible markdown. More instructions are
+provided [[https://github.com/fabioberger/roam-migration][in the repository]].
 
 ** How do I create a note whose title already matches one of the candidates?
 
@@ -1453,8 +1503,10 @@ This situation arises when, for example, one would like to create a note titled
 The solution is dependent on the mini-buffer completion framework in use. Here
 are the solutions:
 
-- Ivy :: call ~ivy-immediate-done~, typically bound to ~C-M-j~. Alternatively, set ~ivy-use-selectable-prompt~ to ~t~, so that "bar" is now selectable.
-- Helm :: Org-roam should provide a selectable "[?] bar" candidate at the top of the candidate list.
+- Ivy :: call ~ivy-immediate-done~, typically bound to ~C-M-j~. Alternatively,
+  set ~ivy-use-selectable-prompt~ to ~t~, so that "bar" is now selectable.
+- Helm :: Org-roam should provide a selectable "[?] bar" candidate at the top of
+  the candidate list.
 
 * Keystroke Index
 :PROPERTIES:
@@ -1482,6 +1534,7 @@ are the solutions:
 # Local Variables:
 # eval: (require 'ol-info)
 # eval: (require 'ox-texinfo+ nil t)
+# eval: (auto-fill-mode +1)
 # before-save-hook: org-make-toc
 # after-save-hook: (lambda nil (progn (require 'ox-texinfo nil t) (org-texinfo-export-to-info)))
 # indent-tabs-mode: nil
diff --git a/org-roam.texi b/org-roam.texi
index 8d8b46e..8db1f26 100644
--- a/org-roam.texi
+++ b/org-roam.texi
@@ -38,15 +38,12 @@ General Public License for more details.
 @insertcopying
 @end titlepage
 
-@contents
-
 @ifnottex
 @node Top
 @top Org-roam User Manual
 
 @noindent
 
-@noindent
 This manual is for Org-roam version 1.2.2.
 
 @quotation
@@ -162,6 +159,13 @@ Ecosystem
 * Org-journal::
 * Note-taking Add-ons::
 
+Note-taking Add-ons
+
+* Org-download::
+* mathpix.el: mathpixel. 
+* Org-noter / Interleave::
+* Bibliography::
+* Spaced Repetition::
 
 FAQ
 
@@ -194,19 +198,31 @@ Org-roam provides several benefits over other tooling:
 
 @itemize
  @item
- Privacy and SecurityEdit your personal wiki completely offline, entirely in your control. Encrypt your notes with GPG@.
+ Privacy and SecurityEdit your personal wiki completely offline, entirely
+in your control. Encrypt your notes with GPG@.
 
 @item
- Longevity of Plain TextUnlike web solutions like Roam research, the notes are first and foremost plain Org-mode files -- Org-roam simply builds up an auxilliary database to give the personal wiki superpowers. Having your notes in plain-text is crucial for the longevity of your wiki. Never have to worry about proprietary web solutions being taken down. Edit your plain-text notes in notepad if all other editors cease to exist
+ Longevity of Plain TextUnlike web solutions like Roam research, the notes
+are first and foremost plain Org-mode files -- Org-roam simply builds up an
+auxilliary database to give the personal wiki superpowers. Having your notes
+in plain-text is crucial for the longevity of your wiki. Never have to worry
+about proprietary web solutions being taken down. Edit your plain-text notes
+in notepad if all other editors cease to exist
 
 @item
- Free and Open SourceOrg-roam is free and open-source, which means that if you feel unhappy with any part of Org-roam, you may choose to extend Org-roam, or open a PR@.
+ Free and Open SourceOrg-roam is free and open-source, which means that if
+you feel unhappy with any part of Org-roam, you may choose to extend Org-roam,
+or open a PR@.
 
 @item
- Leverages the Org-mode ecosystemOver the years, Emacs and Org-mode has developed into a mature system for plain-text organization. Building upon Org-mode already puts Org-roam light-years ahead of many other solutions.
+ Leverages the Org-mode ecosystemOver the years, Emacs and Org-mode has
+developed into a mature system for plain-text organization. Building upon
+Org-mode already puts Org-roam light-years ahead of many other solutions.
 
 @item
- Built on EmacsEmacs is also a fantastic interface for editing text, and we can inherit many of the powerful text-navigation and editing packages available to Emacs.
+ Built on EmacsEmacs is also a fantastic interface for editing text, and we
+can inherit many of the powerful text-navigation and editing packages
+available to Emacs.
 @end itemize
 
 @node Target Audience
@@ -381,9 +397,16 @@ Org-roam will then be autoloaded into Emacs.
 @node Installing from the Git Repository
 @section Installing from the Git Repository
 
-You may install Org-roam directly from the repository on @uref{https://github.com/org-roam/org-roam, GitHub} if you like. This will give you access to the latest version hours or days before it appears on MELPA, and months (or more) before it is added to the Debian or Ubuntu repositories. This will also give you access to various developmental branches that may be available. 
+You may install Org-roam directly from the repository on @uref{https://github.com/org-roam/org-roam, GitHub} if you like.
+This will give you access to the latest version hours or days before it appears
+on MELPA, and months (or more) before it is added to the Debian or Ubuntu
+repositories. This will also give you access to various developmental branches
+that may be available.
 
-Note, however, that development version, and especially any feature branches, may not always be in working order. You'll need to be prepared to do some debugging, or to manually roll-back to working versions, if you install from GitHub.
+Note, however, that development version, and especially any feature branches,
+may not always be in working order. You'll need to be prepared to do some
+debugging, or to manually roll-back to working versions, if you install from
+GitHub.
 
 Installing from GitHub requires that you clone the repository:
 
@@ -393,14 +416,16 @@ git clone https://github.com/org-roam/org-roam.git /path/to/org/roam
 
 where @code{./path/to/org/roam} is the location you will store your copy of the code.
 
-Next, you need to add this location to your load path, and @code{require} the Org-roam library. Add the following code to your @code{.emacs}:
+Next, you need to add this location to your load path, and @code{require} the
+Org-roam library. Add the following code to your @code{.emacs}:
 
 @lisp
 (add-to-list 'load-path "/path/to/org/roam")
 (require 'org-roam)
 @end lisp
 
-You now have Org-roam installed. However, you don't necessarily have the dependencies that it requires. These include:
+You now have Org-roam installed. However, you don't necessarily have the
+dependencies that it requires. These include:
 
 @itemize
 @item
@@ -422,17 +447,25 @@ emacsql
 emacsql-sqlite3
 @end itemize
 
-You can install this manually as well, or get the latest version from MELPA@. You may wish to use @uref{https://github.com/jwiegley/use-package, use-package}, @uref{https://github.com/raxod502/straight.el, straight.el}, or some other tool or tools to help manage this.
+You can install this manually as well, or get the latest version from MELPA@. You
+may wish to use @uref{https://github.com/jwiegley/use-package, use-package}, @uref{https://github.com/raxod502/straight.el, straight.el}, or some other tool or tools to help
+manage this.
 
-If you would like to install the manual for access from Emacs' built-in Info system, you'll need to compile the .texi source file, and install it in an appropriate location.
+If you would like to install the manual for access from Emacs' built-in Info
+system, you'll need to compile the .texi source file, and install it in an
+appropriate location.
 
-To compile the .texi source file, from a terminal navigate to the @code{/doc} subdirectory of the Org-roam repository, and run the following:
+To compile the .texi source file, from a terminal navigate to the @code{/doc}
+subdirectory of the Org-roam repository, and run the following:
 
 @example
 make infodir=/path/to/my/info/files install-info
 @end example
 
-Where @code{/path/to/my/info/files} is the location where you keep info files. This target directory needs to be stored in the variable `Info-default-directory-list`. If you aren't using one of the default info locations, you can configure this with the following in your @code{.emacs} file:
+Where @code{/path/to/my/info/files} is the location where you keep info files. This
+target directory needs to be stored in the variable
+`Info-default-directory-list`. If you aren't using one of the default info
+locations, you can configure this with the following in your @code{.emacs} file:
 
 @lisp
 (require 'info)
@@ -453,9 +486,11 @@ You can also use one of the default locations, such as:
 @emph{usr/local/share/info}
 @end itemize
 
-If you do this, you'll need to make sure you have write-access to that location, or run the above @code{make} command as root.
+If you do this, you'll need to make sure you have write-access to that location,
+or run the above @code{make} command as root.
 
-Now that the info file is ready, you need to add it to the corresponding @code{dir} file:
+Now that the info file is ready, you need to add it to the corresponding @code{dir}
+file:
 
 @example
 install-info /path/to/my/info/files/org-roam.info /path/to/my/info/files/dir
@@ -625,7 +660,8 @@ If you wish to add your own title extraction method, you may push a symbol
 
 Tags are used as meta-data for files: they facilitate interactions with notes
 where titles are insufficient. For example, tags allow for categorization of
-notes: differentiating between bibliographical and structure notes during interactive commands.
+notes: differentiating between bibliographical and structure notes during
+interactive commands.
 
 Org-roam calls @code{org-roam--extract-tags} to extract tags from files. It uses the
 variable @code{org-roam-tag-sources}, to control how tags are extracted. The tag
@@ -633,7 +669,8 @@ extraction methods supported are:
 
 @itemize
 @item
-@code{'prop}: This extracts tags from the @code{#+roam_tags} property. Tags are space delimited, and can be multi-word using double quotes.
+@code{'prop}: This extracts tags from the @code{#+roam_tags} property. Tags are space
+delimited, and can be multi-word using double quotes.
 
 @item
 @code{'all-directories}: All sub-directories relative to @code{org-roam-directory} are
@@ -666,19 +703,20 @@ accepts the absolute file path as its argument. See
 @node File Refs
 @section File Refs
 
-Refs are unique identifiers for files. For example, a note for a website may contain a ref:
+Refs are unique identifiers for files. For example, a note for a website may
+contain a ref:
 
 @example
 #+title: Google
 #+roam_key: https://www.google.com/
 @end example
 
-These keys allow references to the key to show up in the backlinks buffer. For instance,
-with the example above, if another file then links to @uref{https://www.google.com}, that will
-show up as a “Ref Backlink”.
+These keys allow references to the key to show up in the backlinks buffer. For
+instance, with the example above, if another file then links to
+@uref{https://www.google.com}, that will show up as a “Ref Backlink”.
 
-These keys also come in useful for when taking website notes, using the @code{roam-ref} protocol
- (see @ref{Roam Protocol}).
+These keys also come in useful for when taking website notes, using the
+ @code{roam-ref} protocol (see @ref{Roam Protocol}).
 
 @uref{https://github.com/jkitchin/org-ref, org-ref} citation keys can also be used as refs:
 
@@ -692,9 +730,9 @@ These keys also come in useful for when taking website notes, using the @code{ro
 @caption{org-ref-citelink}
 @end float
 
-You may assign multiple refs to a single file, for example when you want multiple papers
-in a series to share the same note, or an article has a citation key and a URL at the same
-time.
+You may assign multiple refs to a single file, for example when you want
+multiple papers in a series to share the same note, or an article has a citation
+key and a URL at the same time.
 
 @node The Templating System
 @chapter The Templating System
@@ -751,8 +789,8 @@ the default template, reproduced below.
 
 @itemize
 @item
-The template has short key @code{"d"}. If you have only one template,
-org-roam automatically chooses this template for you.
+The template has short key @code{"d"}. If you have only one template, org-roam
+automatically chooses this template for you.
 
 @item
 The template is given a description of @code{"default"}.
@@ -766,8 +804,7 @@ The template is given a description of @code{"default"}.
 
 @item
 @code{"%?"} is the template inserted on each call to @code{org-roam-capture--capture}.
-This template means don't insert any content, but place the cursor
-here.
+This template means don't insert any content, but place the cursor here.
 
 @item
 @code{:file-name} is the file-name template for a new note, if it doesn't yet
@@ -804,9 +841,9 @@ provided title. @code{$@{title@}} is then expanded into the provided title durin
 org-capture process. Any variables that do not contain strings, are prompted for
 values using @code{completing-read}.
 
-After doing this expansion, the org-capture's template expansion system
-is used to fill up the rest of the template. You may read up more on
-this on @uref{https://orgmode.org/manual/Template-expansion.html#Template-expansion, org-capture's documentation page}.
+After doing this expansion, the org-capture's template expansion system is used
+to fill up the rest of the template. You may read up more on this on
+@uref{https://orgmode.org/manual/Template-expansion.html#Template-expansion, org-capture's documentation page}.
 
 To illustrate this dual expansion process, take for example the template string:
 @code{"%<%Y%m%d%H%M%S>-$@{title@}"}, with the title @code{"Foo"}. The template is first
@@ -829,12 +866,12 @@ directly to provide its third argument to specify UTC@.
 @node Concepts and Configuration
 @chapter Concepts and Configuration
 
-The number of configuration options is deliberately kept small, to keep
-the Org-roam codebase manageable. However, we attempt to accommodate as
-many usage styles as possible.
+The number of configuration options is deliberately kept small, to keep the
+Org-roam codebase manageable. However, we attempt to accommodate as many usage
+styles as possible.
 
-All of Org-roam's customization options can be viewed via
-@code{M-x customize-group org-roam}.
+All of Org-roam's customization options can be viewed via @code{M-x customize-group
+org-roam}.
 
 @menu
 * Directories and Files::
@@ -955,17 +992,20 @@ registers this link type, and interprets the path as follows:
  @code{[[roam:title]]}links to an Org-roam file with title or alias ``title''
 
 @item
- @code{[[roam:*headline]]}links to the headline ``headline'' in the current Org-roam file
+ @code{[[roam:*headline]]}links to the headline ``headline'' in the current
+Org-roam file
 
 @item
- @code{[[roam:title*headline]]}links to the headline ``headline'' in the Org-roam file with title or alias ``title''
+ @code{[[roam:title*headline]]}links to the headline ``headline'' in the Org-roam
+file with title or alias ``title''
 @end itemize
 
 @code{roam} links support auto-completion via @code{completion-at-point}: simply call
 @code{completion-at-point} within a roam link. Users of @code{company-mode} may want to
 prepend @code{company-capf} to the beginning of variable @code{company-backends}.
 
-To easily insert @code{roam} links, one may wish to use a package like @uref{https://github.com/emacsorphanage/key-chord/, key-chord}. In the following example, typing ``[['' will insert a stub @code{roam} link:
+To easily insert @code{roam} links, one may wish to use a package like @uref{https://github.com/emacsorphanage/key-chord/, key-chord}. In
+the following example, typing ``[['' will insert a stub @code{roam} link:
 
 @lisp
 (key-chord-define org-mode-map "[[" #'my/insert-roam-link)
@@ -1041,13 +1081,13 @@ GPG), which can be enabled for all new files by setting @code{org-roam-encrypt-f
 to @code{t}. When enabled, new files are created with the @code{.org.gpg} extension and
 decryption are handled automatically by EasyPG@.
 
-Note that Emacs will prompt for a password for encrypted files during
-cache updates if it requires reading the encrypted file. To reduce the
-number of password prompts, you may wish to cache the password.
+Note that Emacs will prompt for a password for encrypted files during cache
+updates if it requires reading the encrypted file. To reduce the number of
+password prompts, you may wish to cache the password.
 
 @defopt org-roam-encrypt-files
 
-Whether to encrypt new files.  If true, create files with .org.gpg extension.
+Whether to encrypt new files. If true, create files with .org.gpg extension.
 @end defopt
 
 @node Graphing
@@ -1088,7 +1128,8 @@ ARG may be any of the following values:
 
 @defopt org-roam-graph-executable
 
-Path to the graphing executable (in this case, Graphviz). Set this if Org-roam is unable to find the Graphviz executable on your system.
+Path to the graphing executable (in this case, Graphviz). Set this if Org-roam
+is unable to find the Graphviz executable on your system.
 
 You may also choose to use @code{neato} in place of @code{dot}, which generates a more
 compact graph layout.
@@ -1096,7 +1137,8 @@ compact graph layout.
 
 @defopt org-roam-graph-viewer
 
-Org-roam defaults to using Firefox (located on PATH) to view the SVG, but you may choose to set it to:
+Org-roam defaults to using Firefox (located on PATH) to view the SVG, but you
+may choose to set it to:
 
 @itemize
 @item
@@ -1108,7 +1150,8 @@ a function accepting a single argument: the graph file path.
 
 @code{nil} uses @code{view-file} to view the graph.
 
-If you are using WSL2 and would like to open the graph in Windows, you can use the second option to set the browser and network file path:
+If you are using WSL2 and would like to open the graph in Windows, you can use
+the second option to set the browser and network file path:
 
 @lisp
 (setq org-roam-graph-viewer
@@ -1126,7 +1169,9 @@ If you are using WSL2 and would like to open the graph in Windows, you can use t
 @node Graph Options
 @section Graph Options
 
-Graphviz provides many options for customizing the graph output, and Org-roam supports some of them. See @uref{https://graphviz.gitlab.io/_pages/doc/info/attrs.html} for customizable options.
+Graphviz provides many options for customizing the graph output, and Org-roam
+supports some of them. See @uref{https://graphviz.gitlab.io/_pages/doc/info/attrs.html}
+for customizable options.
 
 @defopt org-roam-graph-extra-config
 
@@ -1200,8 +1245,8 @@ Other options include @code{'ido}, and @code{'ivy}.
 @node Roam Protocol
 @chapter Roam Protocol
 
-Org-roam extends @code{org-protocol} with 2 protocols: the @code{roam-file}
-and @code{roam-ref} protocols.
+Org-roam extends @code{org-protocol} with 2 protocols: the @code{roam-file} and @code{roam-ref}
+protocols.
 
 @menu
 * Installation: Installation (1). 
@@ -1212,7 +1257,8 @@ and @code{roam-ref} protocols.
 @node Installation (1)
 @section Installation
 
-To enable Org-roam's protocol extensions, you have to add the following to your init file:
+To enable Org-roam's protocol extensions, you have to add the following to your
+init file:
 
 @lisp
 (require 'org-roam-protocol)
@@ -1223,7 +1269,8 @@ The instructions for setting up @code{org-protocol} are reproduced below.
 We will also need to create a desktop application for @code{emacsclient}. The
 instructions for various platforms are shown below.
 
-For Linux users, create a desktop application in @code{~/.local/share/applications/org-protocol.desktop}:
+For Linux users, create a desktop application in
+@code{~/.local/share/applications/org-protocol.desktop}:
 
 @example
 [Desktop Entry]
@@ -1242,9 +1289,9 @@ running in your shell:
 xdg-mime default org-protocol.desktop x-scheme-handler/org-protocol
 @end example
 
-To disable the ``confirm'' prompt in Chrome, you can also make Chrome
-show a checkbox to tick, so that the @code{Org-Protocol Client} app will be used
-without confirmation. To do this, run in a shell:
+To disable the ``confirm'' prompt in Chrome, you can also make Chrome show a
+checkbox to tick, so that the @code{Org-Protocol Client} app will be used without
+confirmation. To do this, run in a shell:
 
 @example
 sudo mkdir -p /etc/opt/chrome/policies/managed/
@@ -1345,13 +1392,15 @@ REGEDIT4
 @@="\"C:\\Windows\\System32\\wsl.exe\" emacsclient \"%1\""
 @end example
 
-The above will forward the protocol to WSL@. If you run Emacs natively on Windows, replace the last line with:
+The above will forward the protocol to WSL@. If you run Emacs natively on
+Windows, replace the last line with:
 
 @example
 @@="\"c:\\path\\to\\emacs\\bin\\emacsclientw.exe\"  \"%1\""
 @end example
 
-After executing the .reg file, the protocol is registered and you can delete the file.
+After executing the .reg file, the protocol is registered and you can delete the
+file.
 
 @node The roam-file protocol
 @section The roam-file protocol
@@ -1431,8 +1480,8 @@ Here is a sane default configuration:
 @end lisp
 
 Make sure that @code{org-roam-dailies-directory} appears in @code{:file-name} for your
-notes to be recognized as daily-notes. You can have different templates
-placing their notes in different directories, but the one in
+notes to be recognized as daily-notes. You can have different templates placing
+their notes in different directories, but the one in
 @code{org-roam-dailies-directory} will be considered as the main one in commands.
 
 See @ref{The Templating System} for creating new
@@ -1457,7 +1506,7 @@ specifying the outline-path to a heading:
 @end lisp
 
 The template @code{l} will put its notes under the heading ‘Lab notes’, and the
-template @code{j} will put its notes under the heading ‘Journal’.  When you use
+template @code{j} will put its notes under the heading ‘Journal’. When you use
 @code{:olp}, make sure that the headings are present in @code{:head}.
 
 @node Capturing and finding daily-notes
@@ -1542,10 +1591,11 @@ Perform a check on Org-roam files to ensure cleanliness. If THIS-BUFFER, run
 the check only for the current buffer.
 @end defun
 
-The checks run are defined in @code{org-roam-doctor--checkers}. By default, there are checkers for broken links and invalid @samp{#+roam_*} properties.
+The checks run are defined in @code{org-roam-doctor--checkers}. By default, there are
+checkers for broken links and invalid @samp{#+roam_*} properties.
 
-Each checker is an instance of @code{org-roam-doctor-checker}. To define a checker, use
-@code{make-org-roam-doctor-checker}. Here is a sample definition:
+Each checker is an instance of @code{org-roam-doctor-checker}. To define a checker,
+use @code{make-org-roam-doctor-checker}. Here is a sample definition:
 
 @lisp
 (make-org-roam-doctor-checker
@@ -1557,10 +1607,10 @@ Each checker is an instance of @code{org-roam-doctor-checker}. To define a check
 @end lisp
 
 The @code{:name} property is the name of the function run. The function takes in the
-Org parse tree, and returns a list of @code{(point error-message)}. @code{:description} is a
-short description of what the checker does. @code{:actions} is an alist containing
-elements of the form @code{(char . (prompt . function))}. These actions are defined per
-checker, to perform autofixes for the errors. For each error detected,
+Org parse tree, and returns a list of @code{(point error-message)}. @code{:description} is
+a short description of what the checker does. @code{:actions} is an alist containing
+elements of the form @code{(char . (prompt . function))}. These actions are defined
+per checker, to perform autofixes for the errors. For each error detected,
 @code{org-roam-doctor} will move the point to the current error, and pop-up a help
 window displaying the error message, as well as the list of actions that can be
 taken provided in @code{:actions}.
@@ -1600,7 +1650,8 @@ unlinked references within encrypted files.
 @section Garbage Collection
 
 During the cache-build process, Org-roam generates a lot of in-memory
-data-structures (such as the Org file's AST), which are discarded after use. These structures are garbage collected at regular intervals (see @ref{Garbage Collection,info:elisp#Garbage Collection,,elisp,}).
+data-structures (such as the Org file's AST), which are discarded after use.
+These structures are garbage collected at regular intervals (see @ref{Garbage Collection,info:elisp#Garbage Collection,,elisp,}).
 
 Org-roam provides the option @code{org-roam-db-gc-threshold} to temporarily change
 the threshold value for GC to be triggered during these memory-intensive
@@ -1674,9 +1725,14 @@ operations. To reduce the number of garbage collection processes, one may set
 @node Browsing History with winner-mode
 @subsection Browsing History with winner-mode
 
-@code{winner-mode} is a global minor mode that allows one to undo and redo changes in the window configuration. It is included with GNU Emacs since version 20.
+@code{winner-mode} is a global minor mode that allows one to undo and redo changes in
+the window configuration. It is included with GNU Emacs since version 20.
 
-@code{winner-mode} can be used as a simple version of browser history for Org-roam. Each click through org-roam links (from both Org files and the backlinks buffer) causes changes in window configuration, which can be undone and redone using @code{winner-mode}. To use @code{winner-mode}, simply enable it, and bind the appropriate interactive functions:
+@code{winner-mode} can be used as a simple version of browser history for Org-roam.
+Each click through org-roam links (from both Org files and the backlinks buffer)
+causes changes in window configuration, which can be undone and redone using
+@code{winner-mode}. To use @code{winner-mode}, simply enable it, and bind the appropriate
+interactive functions:
 
 @lisp
 (winner-mode +1)
@@ -1714,10 +1770,9 @@ versions of a tracked Org-roam note.
   (deft-directory "/path/to/org-roam-files/"))
 @end lisp
 
-If the title of the Org file is not the first line, you might not get
-nice titles. You may choose to patch this to use @code{org-roam}'s
-functionality. Here I'm using
-@uref{https://github.com/raxod502/el-patch, el-patch}:
+If the title of the Org file is not the first line, you might not get nice
+titles. You may choose to patch this to use @code{org-roam}'s functionality. Here I'm
+using @uref{https://github.com/raxod502/el-patch, el-patch}:
 
 @lisp
 (use-package el-patch
@@ -1745,18 +1800,16 @@ used as title."
                    (org-roam--get-title-or-slug file))))
 @end lisp
 
-The Deft interface can slow down quickly when the number of files get
-huge. @uref{https://github.com/hasu/notdeft, Notdeft} is a fork of Deft
-that uses an external search engine and indexer.
+The Deft interface can slow down quickly when the number of files get huge.
+@uref{https://github.com/hasu/notdeft, Notdeft} is a fork of Deft that uses an external search engine and indexer.
 
 @node Org-journal
 @subsection Org-journal
 
-@uref{https://github.com/bastibe/org-journal, Org-journal} provides journaling
-capabilities to Org-mode. A lot of its functionalities have been incorporated
-into Org-roam under the name @ref{Daily-notes, , @code{org-roam-dailies}}.  It remains
-a good tool if you want to isolate your verbose journal entries from the ideas
-you would write on a scratchpad.
+@uref{https://github.com/bastibe/org-journal, Org-journal} provides journaling capabilities to Org-mode. A lot of its
+functionalities have been incorporated into Org-roam under the name
+@ref{Daily-notes, , @code{org-roam-dailies}}. It remains a good tool if you want to isolate your verbose
+journal entries from the ideas you would write on a scratchpad.
 
 @lisp
 (use-package org-journal
@@ -1838,7 +1891,9 @@ tight integration between
 @code{org-roam}. This helps you manage your bibliographic notes under
 @code{org-roam}.
 
-For example, though helm-bibtex provides the ability to visit notes for bibliographic entries, org-roam-bibtex extends it with the ability to visit the file with the right @samp{#+roam_key}.
+For example, though helm-bibtex provides the ability to visit notes for
+bibliographic entries, org-roam-bibtex extends it with the ability to visit the
+file with the right @samp{#+roam_key}.
 
 @node Spaced Repetition
 @unnumberedsubsubsec Spaced Repetition
@@ -1871,14 +1926,16 @@ contain:
          (org-roam-db-location . "./org-roam.db"))))
 @end lisp
 
-All files within that directory will be treated as their own separate
-set of Org-roam files. Remember to run @code{org-roam-db-build-cache} from a
-file within that directory, at least once.
+All files within that directory will be treated as their own separate set of
+Org-roam files. Remember to run @code{org-roam-db-build-cache} from a file within
+that directory, at least once.
 
 @node How do I migrate from Roam Research?
 @section How do I migrate from Roam Research?
 
-Fabio has produced a command-line tool that converts markdown files exported from Roam Research into Org-roam compatible markdown. More instructions are provided @uref{https://github.com/fabioberger/roam-migration, in the repository}.
+Fabio has produced a command-line tool that converts markdown files exported
+from Roam Research into Org-roam compatible markdown. More instructions are
+provided @uref{https://github.com/fabioberger/roam-migration, in the repository}.
 
 @node How do I create a note whose title already matches one of the candidates?
 @section How do I create a note whose title already matches one of the candidates?
@@ -1891,10 +1948,12 @@ are the solutions:
 
 @itemize
  @item
- Ivycall @code{ivy-immediate-done}, typically bound to @code{C-M-j}. Alternatively, set @code{ivy-use-selectable-prompt} to @code{t}, so that ``bar'' is now selectable.
+ Ivycall @code{ivy-immediate-done}, typically bound to @code{C-M-j}. Alternatively,
+set @code{ivy-use-selectable-prompt} to @code{t}, so that ``bar'' is now selectable.
 
 @item
- HelmOrg-roam should provide a selectable ``[?] bar'' candidate at the top of the candidate list.
+ HelmOrg-roam should provide a selectable ``[?] bar'' candidate at the top of
+the candidate list.
 @end itemize
 
 @node Keystroke Index