Tweak pad formatting

1 files changed, 7 insertions, 14 deletions

diff --git a/2020/info/31.md b/2020/info/31.md
index 1ea320a0..aafebe3c 100644
--- a/2020/info/31.md
+++ b/2020/info/31.md
@@ -36,19 +36,16 @@ support ongoing oppression against indigenous descended peoples.
 
 ## Q4: Did you write the company backend to complete on Lakota words?
 
+With a Lakota dictionary file, one could probably leverage other company methods for completion.
 
-### With a Lakota dictionary file, one could probably leverage other company methods for completion.
-
-
-### seems to be company-dabbrev, it happens automatically when typing in org-mode at least. unfortunately the only digital Lakota dictionary I'm aware of is non-free, so I'm not sure what to do about that.
+seems to be company-dabbrev, it happens automatically when typing in org-mode at least. unfortunately the only digital Lakota dictionary I'm aware of is non-free, so I'm not sure what to do about that.
 
 -   yeah, I'm not sure, but the dictionary files needed would really just be word-lists, so maybe there is a way to find or produce something of this sort.
 
 
 ## Q3: Why did you decide on e.g. a' for á? In my country's input method (which is Dutch, and in french, german, etc.) the default is to put the accent first, so 'e -> é.
 
-
-### for me, this was my first experience with it and it made more sense in my head to have the modifier come after. its possible i read about postfix notation in a tutorial i found (and lost) that demonstrated Quail input modes. The X11 input has it as a prefix, so I may change it in the future. I'd like to consult with other Lakota speakers and tribal members, however, as it seems worthwhile trying to get consensus from native speakers on usage.
+for me, this was my first experience with it and it made more sense in my head to have the modifier come after. its possible i read about postfix notation in a tutorial i found (and lost) that demonstrated Quail input modes. The X11 input has it as a prefix, so I may change it in the future. I'd like to consult with other Lakota speakers and tribal members, however, as it seems worthwhile trying to get consensus from native speakers on usage.
 
 
 ## Q2:Can you give us a demo of you typing in either Lakota input method?+1+1
@@ -56,18 +53,14 @@ support ongoing oppression against indigenous descended peoples.
 
 ## Q1: Advantages of using Emacs Input Methods over something like xcompose?
 
+→ Compose <https://wiki.archlinux.org/index.php/Xorg/Keyboard_configuration#Configuring_compose_key>
 
-### → Compose <https://wiki.archlinux.org/index.php/Xorg/Keyboard_configuration#Configuring_compose_key>
-
-
-### ah yes, i found something about this when making the X layout, but it was not immediately apparent. Emacs was easier for me to inspect and learn about than X, easier  to iterate on as i was learning how it all worked. Emacs can re-eval the layout definition and give live feedback, while X required a restart to try different things. Emacs is also cross platform, so anyone can easily install this. also, sharing an X config seemed more difficult to me, I don't know how to tell someone to install it properly :(
+ah yes, i found something about this when making the X layout, but it was not immediately apparent. Emacs was easier for me to inspect and learn about than X, easier  to iterate on as i was learning how it all worked. Emacs can re-eval the layout definition and give live feedback, while X required a restart to try different things. Emacs is also cross platform, so anyone can easily install this. also, sharing an X config seemed more difficult to me, I don't know how to tell someone to install it properly :(
 
 
 # Notes
 
 
-## Quail
-
-
-## <https://git.sr.ht/~shoshin/lakota-input.git>
+- Quail
+- <https://git.sr.ht/~shoshin/lakota-input.git>