Update Home

Home.md

@@ -2,7 +2,7 @@
 
 ## Things to consider
 - Write the go service
-  - Turns out it’s actually a client not a server?
+  - Turns out it's actually a client not a server?
   - Poll-based vs webhook-based behavior configurable with parameter
 - Get everyone on twilio account
   - Done!
@@ -14,7 +14,7 @@
     - Document creating compliant sms marketing campaign on twilio
     - Document other twilio setup (sort of unknown complexity right now)
       - jack worked for them and may have better insights, but they were mostly on the security team iirc [T]
-      - HIGH PRIORITY: confirm billing policies to ensure there isn’t a ~secret~ clause where they can just let us rack up a bill and invoice us later in case of some kind of catastrophic failure or spam influx
+      - HIGH PRIORITY: confirm billing policies to ensure there isn't a ~secret~ clause where they can just let us rack up a bill and invoice us later in case of some kind of catastrophic failure or spam influx
 - Signal groups getting large feature updates early 2024, this may change the process dynamically
   - Others: i.e. Discord, WhatsApp, Telegram APIs likely relevant
   - SMS is important for non-smartphone users and less cross-platform stuff
@@ -31,7 +31,7 @@ Code Conventions
 Written in Go
 SQLite database backend - longer term goal for expansion capabilities
 JSON Blob payloads to Twillio flows for actual call and SMS process
-Go federation backend being dev’d by bspar’s company
+Go federation backend being dev'd by bspar's company
 Binaries for ARM and X86 on windows, linux, mac
 Is queue a priority concern up front?
 bspar: yes, because it can have heavy impact on compute speed/resource weight