From 38032e1c7f4b19ee35018e9ec952c93eb77d702f Mon Sep 17 00:00:00 2001
From: couscousdude <couscousdude@users.noreply.github.com>
Date: Tue, 20 Feb 2024 07:08:01 +0000
Subject: [PATCH] style: format

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index c8b5887..b9ce957 100644
--- a/README.md
+++ b/README.md
@@ -21,6 +21,7 @@ eeXiv borrows from a pioneer in digital open access, arXiv.org, and hosts the mo
 [^1]: Whichever idiot decided "arXiv" should be pronounced like "archive" can cope; eeXiv is not changing its name or pronunciation.
 
 ---
+
 <!-- Copilot -->
 <table>
     <img alt="GitHub Copilot" align="left" src="https://raw.githubusercontent.com/KatsuteDev/kdevbot/main/assets/copilot-dark.png#gh-dark-mode-only" width="50">
@@ -58,4 +59,3 @@ The dummies guide to maintaining a Next.js project:
   - **Footnote**: why don't I have to use the utilities in [`db/loaders.ts`](./src/app/db/loaders.ts) to asynchronously load the data in server side components?
     - Next.js will automatically pre-render all server side components into static HTML, which means there will be no performance impact (and in fact performance gain at build time)
       to loading the entire objects into memory.
-