Update 2301-info-endpoint.md

proposals/2301-info-endpoint.md

@@ -19,7 +19,7 @@ We have many different APIs for querying server capabilities and configuration:
  users know that they're trying to log into the right server, and see useful
  information 'from the outside' about that server.
 
-## Proposal
+## Proposal
 
 Rather than creating yet another unauthenticated capabilities/config endpoint,
 we rename `/versions` into `/info` and support adding additional namespaced
@@ -72,4 +72,4 @@ We could then also inherit i18n support for events from the extensible events sp
 However, this is slightly harder for the client to achieve; first it has to call `/info` to get
 the room ID, and then `/room/$room_id/state` to actually peek in and grab the server branding info.
 
-This is probably a more elegant solution tbh; thoughts welcome?
+This is probably a more elegant solution tbh; thoughts welcome?