2023-11-04 minutes: minor fixes to typos, etc. (#73)

* 2023-11-04 minutes: minor fixes to typos, etc.

* 2023-11-04 minutes: more small fixes

Author: aaaaaa123456789

website/meetings/2023-11-04-sc.md

@@ -6,7 +6,7 @@ sidebar: false
 
 Written by avivace.
 
-**November 4th, 2023**. 4:00 PM - 6:30 PM CEST. Discord VC.
+**November 4th, 2023**. 15:00 — 17:30 UTC. Discord VC.
 
 ##### Invited
 
@@ -19,7 +19,7 @@ PinoBatch, avivace, ISSO, Calindro, Duo, nitro2k01, QuangDX, superdisk, kva64, S
 
 ##### About those meetings
 
-Partecipants are asked to fill in discussion points beforehand. The results of these discussions (decisions, suggestions, comments, ..) are reported as the sub items.
+Participants were asked to fill in discussion points beforehand. The results of these discussions (decisions, suggestions, comments, etc.) are reported as subitems.
 
 Discussion points marked \* were not brought up due to lack of time.
 
@@ -30,13 +30,13 @@ Anyone can reach out in `#meta` on the Discord server to comment/discuss on any
 -   avivace:
 
     -   Q to ISSO: RGBDS Rust port plans?
-        -   Scope: Full port from the old codebase, can’t be 1to1
+        -   Scope: Full port from the old codebase, can’t be 1-to-1
         -   Architecture design in progress
         -   Motivation: C not attractive anymore for potential contributors. Showing its age. Technicalities (std::vector). Rust is fancier, more active community.
         -   (Personal) De-risking/Viability study
         -   Question from Pino: will this affect availability of binaries?
     -   Homebrew Hub: developments and expanding to NES \*
-    -   Gbcompo23: [...] \*
+    -   Gbcompo23: \[...\] \*
     -   Funding: how to? \*
     -   Creating the steering committee: Roles? \*
     -   Q to Sanqui: how to run these meetings? Minutes \*
@@ -69,23 +69,23 @@ Anyone can reach out in `#meta` on the Discord server to comment/discuss on any
 
 -   nitro2k01:
 
-    -   Potentially add long a term solution for the IRC bridge as a point/ responsibility.
+    -   Potentially add a long-term solution for the IRC bridge as a point/responsibility.
         -   Someone other than @avivace needs to volunteer (=> @nitro2k01) and get SSH access and/or a webhook token to delegate the responsibility of handling the bridge
     -   Future of the forums \*
 
 -   Kva64:
 
-    -   social media handling — general outline and feedback request
+    -   Social media handling — general outline and feedback request
         -   Not only game releases/showcase content can be shared, but projects themselves may have cool milestones to share
-        -   Allow developers, maintainers… to raise up things that can be promoted, so people helping with social media don’t have to “chase” those. Should those go in #showcase? Should #showcase be split?
+        -   Allow developers, maintainers, etc. to raise up things that can be promoted, so people helping with social media don’t have to “chase” those. Should those go in #showcase? Should #showcase be split?
         -   Encourage (PSA?) developers to post in #showcase
             Move all showcase channels to a separate category, and rename “showcase” to “wip-showcase”?
             Split #releases into e.g. #releases-games and #releases-tooling
         -   To discuss in #meta: opt-in/opt-out status of showcase channels. A suggestion: make sharing opt-out in #releases-\*, and opt-in in #wip-showcase
-    -   policy on sharing and promoting commercial projects?
-        -   DUO : do not shy away from promoting them because it’s a motivation to some; however, restrictions should be put to avoid being taken advantage of
-        -   Should the cooldown (if any) should apply per project, per user, ..?
-    -   need for using any newly emerging social media platforms (e.g threads and bluesky)?
+    -   Policy on sharing and promoting commercial projects?
+        -   DUO: do not shy away from promoting them because it’s a motivation to some; however, restrictions should be put to avoid being taken advantage of
+        -   Should the cooldown (if any) apply per project, per user...?
+    -   Need for using any newly-emerging social media platforms (e.g. Threads and Bluesky)?
         -   Threads and Bluesky currently have very little reach, so maybe not
         -   Other platforms (e.g. Instagram): maybe, but this may require more people to handle them
         -   Creating a channel to coordinate them