Limerence

2020-07-21 23:49:24 -07:00
parent 4e6230fa2a
commit 1f1bf40d31
11 changed files with 2 additions and 2 deletions
--- a/content/ally/037.md
+++ b/content/ally/037.md
@ -10,4 +10,4 @@ weight: 37

 > Keats? Now? Really?

-<a class="pulse" href="/limerance">I can't help it.</a>
+<a class="pulse" href="/limerence">I can't help it.</a>
--- a/content/limerence/001.md
+++ b/content/limerence/001.md
--- a/content/limerence/002.md
+++ b/content/limerence/002.md
--- a/content/limerence/003.md
+++ b/content/limerence/003.md
--- a/content/limerence/004.md
+++ b/content/limerence/004.md
--- a/content/limerence/005.md
+++ b/content/limerence/005.md
--- a/content/limerence/006.md
+++ b/content/limerence/006.md
--- a/content/limerence/007.md
+++ b/content/limerence/007.md
@ -3,7 +3,7 @@ date: 2020-07-21
 weight: 7
 ---

-For the most part, I try to just keep limerance to myself. I'll talk about it with Robin sometimes, or maybe JD, but it's not really something I'll bring up with anyone else, least of all with the limerent object. Why would I? Why would I put that burden on them when I'm not convinced it's worth acting on? Especially if it's something that happens shortly after meeting them.
+For the most part, I try to just keep limerence to myself. I'll talk about it with Robin sometimes, or maybe JD, but it's not really something I'll bring up with anyone else, least of all with the limerent object. Why would I? Why would I put that burden on them when I'm not convinced it's worth acting on? Especially if it's something that happens shortly after meeting them.

 > Why not?

--- a/content/limerence/008.md
+++ b/content/limerence/008.md
--- a/content/limerence/009.md
+++ b/content/limerence/009.md
--- a/content/limerence/_index.html
+++ b/content/limerence/_index.html