actually use markdown features

pages should look better in yiki now since i improved that too

README.md

@@ -6,7 +6,8 @@ An alternative to MSNPiki that aims to actually document things they didn't.
 npm i
 set WIKINAME=yellows' MSNP wiki
 # this should be an absolute path on a domain to where the files will be put
-set VPREFIX=https://example.com/
+set VPREFIX=/
+set DOMAIN=example.com
 mkdir build
 npm run build
 cp ./node_modules/yiki/yiki.css build/

docs/command-table.md

@@ -5,8 +5,9 @@ This is a list of all known MSNP commands and their originating version.
 | `COMMAND` | Payload (Y/N) | Client to Server (Y/N) | Server to Client (Y/N) | Originating Version | Changed? (version list) |
 | ----- | - | - | -| ------ | ----- |
 | [`VER`](commands/ver.md) | N | Y | N | [MSNP2](versions/msnp2.md)  | every MSNP version, but retaining base syntax, removed in MSNP24 |
-| `INF` | N | Y | N | [MSNP2](versions/msnp2.md)  | [MSNP3](versions/msnp3.md) (removed CTP), [MSNP8](versions/msnp8.md) (removed; automatic disconnect) |
+| [`INF`](commands/inf.md) | N | Y | N | [MSNP2](versions/msnp2.md)  | [MSNP3](versions/msnp3.md) (removed CTP), [MSNP8](versions/msnp8.md) (removed; automatic disconnect) |
 | `CVR` | N | Y | N | [MSNP2](versions/msnp2.md)  | [MSNP8](versions/msnp8.md) (parameter 8) |
 | `CVQ` | N | Y | N | [CVR0](versions/cvr0.md)   | [MSNP8](versions/msnp8.md) (parameter 8) |
 | `USR` | N | Y | N | [MSNP2](versions/msnp2.md)  | [MSNP3](versions/msnp3.md) (removed CTP), [MSNP6](versions/msnp7.md) (added verified bit to OK), [MSNP8](versions/msnp8.md) (TWN auth, removed MD5 auth, added unknown bit to OK), [MSNP10](versions/msnp10.md) (removed current display name in favor of PRP MFN), [MSNP15](versions/msnp15.md) (SSO auth) |
-| `XFR` | N | Y | Y?| [MSNP2](versions/msnp2.md)  | [MSNP3](versions/msnp3.md) (parameter 3), [MSNP7](versions/msnp7.md) (parameter 4) |
+| [`XFR`](commands/xfr.md) | N | Y | Y?| [MSNP2](versions/msnp2.md)  | [MSNP3](versions/msnp3.md) (parameter 3), [MSNP7](versions/msnp7.md) (parameter 4) |
+| [`OUT`](commands/out.md) | N | Y | Y | [MSNP2](versions/msnp2.md) | [MSNP10](versions/msnp10.md) (MIG and TOU disconnect reasons added), [MSNP11](versions/msnp11.md) (RCT reason added with parameter for amount of minutes until attempted reconnect.) |

docs/commands/inf.md

@@ -0,0 +1,41 @@
+# Introduction
+`INF` is a command introduced with [MSNP2](../versions/msnp2.md).
+
+It is a Dispatch Server and Notification Server command, without either a request or response payload.
+
+It specifies which authentication methods the client is allowed to use.
+
+This command can only be sent once. Any further uses of this command in the same session is Undefined Behavour.
+
+# Client/Request
+`INF TrID`
+
+# Server/Response
+`INF TrID security-package {security-package ...}`
+
+Where (unlikely multiple) `security-package` parameters being the avaliable authentication methods your client is allowed to use.
+
+# Examples
+
+## Two types supported
+*This configuration is only supported in [MSNP2](../versions/msnp2.md).*
+```
+C: INF 1
+S: INF 1 MD5 CTP
+```
+
+## One type supported
+```
+C: INF 2
+S: INF 2 MD5
+```
+
+## Command removed
+*Since [MSNP8](../versions/msnp8.md).*
+```
+C: INF 3
+```
+Server disconnects client.
+
+# Known changes
+* Removed in [MSNP8](../versions/msnp8.md). [USR](usr.md) assumes the authentication method is `TWN`.

docs/commands/out.md

@@ -0,0 +1,63 @@
+# Introduction
+`OUT` is a command introduced with [MSNP2](../versions/msnp2.md).
+
+It exists in all servers, without either a request or response payload.
+
+It disconnects either the server or the client gracefully.
+
+This command does not require a Transaction ID.
+
+# Client/Request
+`OUT`
+
+# Server/Response
+`OUT {reason}`
+
+Where `reason` can be:
+* `OTH`: Other client logged in to this account.
+* `SSD`: Server is shutting down.
+* `MIG`: [MSNP10](../versions/msnp10.md) and higher: Contact list has been migrated.
+* `TOU`: [MSNP10](../versions/msnp10.md) and higher: You need to accept the Terms Of Use.
+* `RCT`: [MSNP11](../versions/msnp11.md) and higher: Temporary server closure, please reconnect in (parameter 2) minutes.
+
+`OUT RCT {minutes}`
+
+Where `minutes` is the amount of minutes the client should wait before trying to log in automatically again.
+
+# Examples
+
+## Client-initiated
+```
+C: OUT
+S: OUT
+```
+
+Server disconnects client.
+
+## Logged in from another client
+```
+S: OUT OTH
+```
+
+## Server is shutting down
+```
+S: OUT SSD
+```
+
+## ABCH Migration
+*This can only happen in [MSNP10](../versions/msnp10.md) exclusively.*
+```
+S: OUT MIG
+```
+
+## Terms of Use update
+*This can only happen since [MSNP10](../versions/msnp10.md).*
+```
+S: OUT TOU
+```
+
+## Forced Reconnect
+*This can only happen since [MSNP11](../versions/msnp11.md).*
+```
+S: OUT RCT 6
+```

docs/commands/ver.md

@@ -1,25 +1,24 @@
+# Introduction
 `VER` is a command introduced with [MSNP2](../versions/msnp2.md).
 
 It is a Dispatch Server and Notification Server command, without either a request payload or response payload.
 
 It specifies which protocols the client can accept, and which one the server likes the best.
 
+This command can only be sent once. Any further uses of this command in the same session is Undefined Behavour.
+
 # Client/Request
-```
+`VER TrID dialect-name {dialect-name ...}`
-VER TrID dialect-name {dialect-name ...}
+
-```
+Where (possibly multiple) `dialect-name` parameters being the versions of the protocol your client can use.
-Where (possibly multiple) dialect-name(s) being the versions of the protocol your client can use.
 
 # Server/Response
-```
+`VER TrID preferred-dialect-name`
-VER TrID preferred-dialect-name
+
-```
 Where `preferred-dialect-name` is the preferred version of the protocol the server will continue to use. The highest is usually preferred, unless it isn't supported by the server.
 
 If the server's `preferred-dialect-name` is `0`, that means it doesn't want to use any of the protocols you have specified. A forced disconnect is to be expected in this circumstance.
 
-This command can only be sent once. Any further uses of this command in the same session is Undefined Behavour.
-
 # Examples
 
 ## Unsupported Protocols

docs/commands/xfr.md

@@ -0,0 +1,86 @@
+# Introduction
+`XFR` is a command introduced with [MSNP2](../versions/msnp2.md).
+
+It is a Dispatch Server and Notification Server command, without either a request or response payload.
+
+It tells the client what server to connect to for the request.
+
+# Client/Request
+`XFR TrID server-type`
+
+Where `server-type` is either `SB` (for a switchboard server), or `NS` (for a new Notification server).
+
+# Server/Response
+
+## XFR NS
+`XFR TrID NS address:port {0} {current-server}`
+
+Where `address:port` is the server you have requested or being referred to is.
+
+In [MSNP3](../versions/msnp3.md) or higher, `0` is always 0.
+
+In [MSNP7](../versions/msnp7.md) or higher, `current-server` is the current server you are connected to.
+
+## XFR SB
+`XFR TrID SB address:port authentication-method authentication-parameter`
+
+Where `address:port` is the server you have requested is. 
+
+Where `authentication-method` is always `CKI`.
+
+Where `authentication-parameter` is the "cookie" you need to log in to Switchboard.
+
+# Examples
+
+## Client requests a new Switchboard connection
+
+```
+C: XFR 1 SB
+S: XFR 1 SB 10.0.1.200:1865 CKI 123456789.123456789.123456789
+```
+
+## Client requests a new Notification server
+*Only used as-is in Beta 2 as the first command sent to a Dispatch Server.*
+```
+C: XFR 2 NS
+S: XFR 2 NS 10.0.0.5:1863
+```
+Client disconnects from server
+
+Client opens a connection to 10.0.0.5:1863
+
+## Client referred from Dispatch Server
+
+### Very Old
+*Only in [MSNP2](../versions/msnp2.md) Exclusively.*
+```
+C: USR 3 MD5 I example@hotmail.com
+S: XFR 3 NS 10.0.0.5:1863
+```
+Client disconnects from server
+
+Client opens a connection to 10.0.0.5:1863
+
+### Classic
+*Only in [MSNP3](../versions/msnp3.md) to [MSNP6](../versions/msnp6.md).*
+```
+C: USR 4 MD5 I example@hotmail.com
+S: XFR 4 NS 10.0.0.5:1863 0
+```
+Client disconnects from server
+
+Client opens a connection to 10.0.0.5:1863
+
+### Modern
+*Since [MSNP7](../versions/msnp7.md).*
+```
+C: USR 5 MD5 I example@hotmail.com
+S: XFR 5 NS 10.0.0.5:1863 0 10.0.0.1:1863
+```
+Client disconnects from server
+
+Client opens a connection to 10.0.0.5:1863
+
+# Known changes
+* [MSNP3](..versions/msnp3.md) adds a new parameter that is always 0.
+* [MSNP7](..versions/msnp7.md) adds a new parameter that is the current server you are connected to.

docs/index.md

@@ -21,9 +21,15 @@ Why not visit the [Command Table](command-table.md)?
 More is to come soon! Hopefully!
 
 # Wanted Information
+* [MSNP2](versions/msnp2.md): What is the format of the initial `text/x-msmsgsemailnotification`?
+* [MSNP3](versions/msnp3.md): How is `creds` generated for URLs native to this version?
+* [MSNP4](versions/msnp4.md): Anything for this one.
 * [MSNP6](versions/msnp6.md): What makes the "Account must be verified before using the service" dialog show up?
 * [MSNP6](versions/msnp6.md): Does it really acknoledge the account verified bit? I couldn't get the toast to show up in Client Version 3.6.003x.
 * [MSNP8](versions/msnp8.md): Did FND exist? Rumors said it did shortly before it got killed in all protocols.
+* [MSNP10](versions/msnp10.md): Asynchronous `BPR MFN`s from the server. Does it really?
+* [MSNP11](versions/msnp11.md): How does `ABCHMigrated: 0` really work now? `OUT MIG` still exists.
+* All Protocols: Any error code known to exist but is missing from the pages.
 
 # Common (or not) Terms
 * Official Client: MSN Messenger (Service) or Windows Live Messenger.
@@ -46,6 +52,7 @@ More is to come soon! Hopefully!
 * New-line/Newline: A Carriage Return character followed by a Line Feed character. Seperates commands in the protocol.
 * Carriage Return: To return the page-writing apparatus to the left of the page.
 * Line Feed: To move the page-writing apparatus down a "line".
+* TrID: Transaction ID. Links the server's response to the client's request.
 
 # Where do I find or edit these page's source?
 The git repo is avaliable at <https://git.kevinthe.horse/yellows111/msnp-wiki>.

docs/versions/cvr0.md

@@ -1,8 +1,11 @@
+# Introduction
+
 CVR0 is a subprotocol of the Mobile Status Notification Protocol.
 It was introduced officially in Client Version 1.0.0863, along with [MSNP2](msnp2.md).
 
 It is used for requesting the latest client information in case no other protocols were supported.
 
+# Command information
 It introduces the commands:
 * CVQ
 
@@ -10,12 +13,16 @@ It introduces the commands:
 
 *No commands were known to be removed in this version*
 
-Known changes (from Beta 2):
+# Known changes
+(from Beta 2):
 * Changed CVR to CVQ
 * CVQ: Added fallback URL to response (parameter 5)
-* [[MSNP8](msnp8.md) and higher] Added current principle address to request (parameter 8)
+* [[MSNP8](msnp8.md) and higher]: Added current principle address to request (parameter 8)
 
-Client-server communication example (MSNP2-MSNP7):
+# Client-server communication examples
+
+## Older protocols
+* [MSNP2](msnp2.md)-[MSNP7](msnp7.md), example using Client Version 1.0.
 ```
 C: VER 1 MSNP2 CVR0
 S: VER 1 CVR0
@@ -24,9 +31,8 @@ S: CVQ 2 5.0.0537 5.0.0537 1.0.0863 http://download.microsoft.com/download/msnme
 ```
 Server disconnects client.
 
----
+## Newer protocols
-
+* [MSNP8](msnp8.md) and higher, example using Client Version 6.1.
-Client-server communication example (MSNP8+, example using Client 6.1):
 ```
 C: VER 1 MSNP10 MSNP9 CVR0
 S: VER 1 CVR0

docs/versions/msnp10.md

@@ -1,6 +1,10 @@
+# Introduction
+
 MSNP10 is the ninth released version of the Mobile Status Notification Protocol.
 It was introduced officially in Client Version 6.1.0155.
 
+# Command information
+
 It introduces the notification service commands:
 * ADC
 * SBP
@@ -13,21 +17,22 @@ The following commands were removed in this version:
 * ADD (automatic disconnection)
 * REA (automatic disconnection?)
 
-Known changes (from [MSNP9](msnp9.md)):
+# Known changes
-* Added new initial profile variable TOUNeeded. If exists and set to 1,
+(from [MSNP9](msnp9.md)):
+* Added new initial profile variable `TOUNeeded`. If exists and set to 1,
   a dialog box to review the Messenger Service Terms of Use is shown to the user.
 * Changed SYN request and response.
   Client: `SYN transactionID listVersion settingsVersion`.
   Server: `SYN transactionID listVersion settingsVersion numberOfContacts numberOfGroups`.
-  settingsVersion is always 0.
+  `settingsVersion` is always 0.
 * Current display name is removed from USR, now is returned with other user properties (PRPs) in SYN.
 * PRP MFN replaces REA (current passport). SBP (contact's address) MFN replaces other uses of REA.
-* Added new initial profile variable ABCHMigrated. If set to 1, some commands are altered, such as:
+* Added new initial profile variable `ABCHMigrated`. If set to 1, some commands are altered, such as:
   SYN: The request and response's list versions are now ISO 8601 with 7 subsecond digits, 
        usually with a -07:00 timezone offset.
        the previously unused second parameter (both request and response) is used as the Last Settings Version,
 	   and follows the same time format as List Versions now do.
-  LST: GUID specified as C= parameter, group IDs are now GUIDs.
+  LST: GUID specified as `C=` parameter, group IDs are now GUIDs.
   ADC, REM: uses GUIDs instead of contact emails if the list is FL, and also for groups.
   LSG, ADG: Uses GUIDs instead of IDs.
   SBP: Uses the contact's GUID instead of the Contact Address.
@@ -36,13 +41,13 @@ Known changes (from [MSNP9](msnp9.md)):
 * Asynchronous BPRs also do not include the new list version number,
   and now provide Friendly Name (MFN) changes instead of sending entire NLNs [needs to be confirmed].
 * Added a new list: Pending List/PL (bit 5, decimal 16). Is meant for unhandled contact added you notifications.
-* Added new server-side OUT reasons: MIG, if the server has migrated you to ABCH,
+* Added new server-side [OUT](../commands/out.md) reasons: MIG, if the server has migrated you to ABCH,
   and TOU, for not accepting the Service Terms of Use.
 * Official Client: Now handles the 604 error code again, which was last seen in Client Version 3.6.003x.
   Error code 913 is no longer handled after being implemented in Client Version 4.5.
-* First protocol version to remove a core command implemented since MSNP2 draft (ADD).
+* First protocol version to remove a core command implemented since [MSNP2](msnp2.md) draft (ADD).
 
-Client-server communication example:
+# Client-server communication example
 ```
 C: VER 1 MSNP10 MSNP9 CVR0
 S: VER 1 MSNP10

docs/versions/msnp11.md

@@ -1,6 +1,10 @@
+# Introduction
+
 MSNP11 is the tenth released version of the Mobile Status Notification Protocol.
 It was introduced officially in Client Version 7.0.0777.
 
+# Command information
+
 It introduces the notification service commands:
 * GCF
 * SBS
@@ -13,13 +17,18 @@ It introduces the notification service commands:
 
 *No commands were known to be removed in this version*
 
-Known changes (from [MSNP10](msnp10.md)):
+# Known changes
-* All ABCHMigrated changes are now the default - ABCHMigrated: 0 is Undefined Behavour from now on.
+(from [MSNP10](msnp10.md)):
+* [OUT](../commands/out.md) RCT `TimeBeforeRetry` now exists.
+  `TimeBeforeRetry` is a numerical value in minutes that specifies the amount
+  of time in minutes the client should wait before reconnecting.
+* All `ABCHMigrated` changes are now the default - `ABCHMigrated: 0` is Undefined Behavour from now on.
 * Official Client: WebMessenger now canonically exists - Client Capability 512 is used for this.
-* Official Client: Notifications (NOTs) with encoded NotificationData documents are supported for spaces.
+* Official Client: Notifications (NOTs) with encoded `NotificationData` documents are supported for spaces.
 * Official Client: Messenger Config requests now support regional arguments via SOAP.
+* Official Client: [OUT](../commands/out.md) SSD is actually implemented now.
 
-Client-server communication example:
+# Client-server communication example
 ```
 C: VER 1 MSNP10 MSNP9 CVR0
 S: VER 1 MSNP10

docs/versions/msnp12.md

@@ -1,6 +1,10 @@
-MSNPXX is the eleventh released version of the Mobile Status Notification Protocol.
+# Introduction
+
+MSNP12 is the eleventh released version of the Mobile Status Notification Protocol.
 It was introduced officially in Client Version 7.5.0299.
 
+# Command information
+
 It introduces the notification service commands:
 * LKP
 
@@ -10,14 +14,15 @@ It introduces the notification service commands:
 
 *No commands were known to be removed in this version*
 
-Known changes (from [MSNP11](msnp11.md)):
+# Known changes
+(from [MSNP11](msnp11.md)):
 * Network IDs are introduced, each bit represents a contact's service, with bit 0/decimal 1 being MSNP.
 * Switchboard commands JOI and IRO have a new parameter for the Client Capabilities of the relevant user.
 * LST has the Network ID after the list bits (on any list), but before the Group ID (if on FL).
 * Official Client: Uses Passport 3.0 (via the Microsoft Identity Common Runtime Library).
 * Official Client: Dropped support for older operating systems, Now requires Windows XP or higher.
 
-Client-server communication example:
+# Client-server communication example
 ```
 C: VER 1 MSNP12 MSNP11 MSNP10 CVR0
 S: VER 1 MSNP12

docs/versions/msnp2.md

@@ -1,12 +1,15 @@
+# Introduction
+
 MSNP2 is the first released version of the Mobile Status Notification Protocol.
 It was introduced officially in Client Version 1.0.0863, along with [CVR0](cvr0.md).
 
+# Command information
 It introduces the dispatch service commands:
-* INF
+* [INF](../commands/inf.md)
-* OUT
+* [OUT](../commands/out.md)
 * USR
 * [VER](../commands/ver.md)
-* XFR
+* [XFR](../commands/xfr.md)
 
 It introduces the notification service commands:
 * ADD
@@ -16,12 +19,12 @@ It introduces the notification service commands:
 * FND (not in draft)
 * FLN
 * GTC
-* INF
+* [INF](../commands/inf.md)
 * ILN
 * LST
 * MSG
 * NLN
-* OUT
+* [OUT](../commands/out.md)
 * PNG (not in draft)
 * QNG (not in draft)
 * REA (not in draft)
@@ -32,7 +35,7 @@ It introduces the notification service commands:
 * URL (not in draft)
 * USR
 * [VER](../commands/ver.md)
-* XFR
+* [XFR](../commands/xfr.md)
 
 It introduces the switchboard service commands:
 * ACK
@@ -43,7 +46,7 @@ It introduces the switchboard service commands:
 * JOI
 * MSG
 * NAK
-* OUT
+* [OUT](../commands/out.md)
 * USR
 
 It introduces the error codes:
@@ -93,10 +96,11 @@ It introduces the error codes:
 
 *No commands were known to be removed in this version*
 
-Known changes (from Beta 2):
+# Known changes
+(from Beta 2)
 * Dispatch servers now go through the normal user proceedure until `USR x MD5 I`.
 
-Client-server communication example:
+# Client-server communication example
 ```
 C: VER 1 MSNP2 CVR0
 S: VER 1 MSNP2
@@ -147,4 +151,4 @@ Client disconnects from server
 ```
 S: OUT
 ```
-Server disconnects client
+Server disconnects client

docs/versions/msnp3.md

@@ -1,6 +1,10 @@
+# Introduction
+
 MSNP3 is the second released version of the Mobile Status Notification Protocol.
 It was introduced officially in Client Version 2.0.0085.
 
+# Command information
+
 It introduces the notification service commands:
 * IMS
 
@@ -13,8 +17,9 @@ It introduces the error codes:
 
 *No commands were known to be removed in this version*
 
-Known changes (from [MSNP2](msnp2.md)):
+# Known changes
-* XFR: Added a new parameter that is always 0. No use is known or documented.
+(from [MSNP2](msnp2.md)):
+* [XFR](../commands/xfr.md): Added a new parameter that is always 0. No use is known or documented.
 * Added Passport Site IDs to URL (parameter 3).
 * Initial profile: Added Passport intergration fields.
 * Font information has been added to Switchboard MSGs.
@@ -26,11 +31,11 @@ Known changes (from [MSNP2](msnp2.md)):
 * Clear-Text Password (CTP) authentication method discontinued.
 * Entire content of initial email notification changed from
   `text/x-msmsgsemailnotification` to `application/x-msmsgsinitialemailnotification`,
-  the format is likely different. Now includes unread email count. \[Examination needed\]
+  the format is likely different. Now includes unread email count. [Examination needed]
 * Official Client: Changed form that URL uses to login drastically.
   New format is undocumented, but now has MD5 `creds` instead of the plain-text `passwd`.
 
-Client-server communication example:
+# Client-server communication example
 ```
 C: VER 1 MSNP3 MSNP2 CVR0
 S: VER 1 MSNP3

docs/versions/msnp4.md

@@ -1,13 +1,18 @@
+# Introduction
+
 MSNP4 is the third released version of the Mobile Status Notification Protocol.
 It was introduced officially in Client Version 2.1.1047.
 
+# Command information
+
 *No commands for any service were known to be introduced in this version*
 
 *No error codes were known to be introduced in this version*
 
 *No commands were known to be removed in this version*
 
-Known changes (from [MSNP3](msnp3.md)):
+# Known changes
+(from [MSNP3](msnp3.md)):
 * ?
 * ?
 * ?
@@ -19,7 +24,7 @@ Known changes (from [MSNP3](msnp3.md)):
   Probably a new initial profile field by then.
   (Client doesn't parse 923 yet either)
 
-Client-server communication example:
+# Client-server communication example
 ```
 C: VER 1 MSNP4 MSNP3 CVR0
 S: VER 1 MSNP4

docs/versions/msnp5.md

@@ -1,6 +1,10 @@
+# Introduction
+
 MSNP5 is the fourth released version of the Mobile Status Notification Protocol.
 It was introduced officially in Client Version 3.0.0283.
 
+# Command information
+
 It introduces the notification service commands:
 * BPR
 * NOT
@@ -14,8 +18,9 @@ It introduces the notification service commands:
 
 *No commands were known to be removed in this version*
 
-Known changes (from [MSNP4](msnp4.md)):
+# Known changes
-* Non-protocol: Official website stopped updating the whatsnew.asp page between this (MSNP5) and MSNP7.
+(from [MSNP4](msnp4.md)):
+* Non-protocol: Official website stopped updating the whatsnew.asp page between this (MSNP5) and [MSNP7](msnp7.md).
 * Official Client: Introduced the toast notification system. Notifications can now stack vertically.
 * Official Client: Log in notifications are now handled by the newly introduced toast system.
 * Official Client: Introduced emoticons.
@@ -23,7 +28,7 @@ Known changes (from [MSNP4](msnp4.md)):
 * Introduced first payload commands (SDC, PAG) to be sent to the switchboard from the client.
 * Official Client: Error code 913 is no longer handled. It was last seen in Client Version 2.1.
 
-Client-server communication example:
+# Client-server communication example
 ```
 C: VER 1 MSNP5 MSNP4 CVR0
 S: VER 1 MSNP5

docs/versions/msnp6.md

@@ -1,6 +1,10 @@
+# Introduction
+
 MSNP6 is the fifth released version of the Mobile Status Notification Protocol.
 It was introduced officially in Client Version 3.6.0038.
 
+# Command information
+
 It introduces the notification service commands:
 * CHL
 * IPG
@@ -12,7 +16,8 @@ It introduces the notification service commands:
 
 *No commands were known to be removed in this version*
 
-Known changes (from [MSNP5](msnp5.md)):
+# Known changes
+(from [MSNP5](msnp5.md)):
 * USR OK now has a verified bit (parameter 4), if 0, shows a warning to verify the account.
   Note: Your display name will be forced to be
   `example@hotmail.com (E-Mail Address Not Verified)`, and cannot be changed.
@@ -21,7 +26,7 @@ Known changes (from [MSNP5](msnp5.md)):
 * An example client secret is `Q1P7W2E4J9R8U3S5`, which is tied to `msmsgs@msnmsgr.com`.
 * First protocol version added in a patch release (3.6.0025 and 3.6.0026 do not support MSNP6).
 
-Client-server communication example:
+# Client-server communication example
 ```
 C: VER 1 MSNP6 MSNP5 MSNP4 CVR0
 S: VER 1 MSNP6

docs/versions/msnp7.md

@@ -1,6 +1,10 @@
+# Introduction
+
 MSNP7 is the sixth released version of the Mobile Status Notification Protocol.
 It was introduced officially in Client Version 4.5.0121.
 
+# Command information
+
 It introduces the notification service commands:
 * ADG
 * REG
@@ -15,7 +19,8 @@ It introduces the error codes:
 
 *No commands were known to be removed in this version*
 
-Known changes (from [MSNP6](msnp6.md)):
+# Known changes
+(from [MSNP6](msnp6.md)):
 * Added contact groups. All FL contacts now have an extra number array for what groups they are in.
   The "Other Contacts" group can NOT be removed.
 * ADD and REM now have group parameters if the list is FL.
@@ -23,13 +28,13 @@ Known changes (from [MSNP6](msnp6.md)):
 * Adds with the list set to FL with a group ID only adds that user from the respective group, not to the FL.
 * SYN now includes LSG entries for groups.
 * LST (either from itself or a SYN response ) now includes contact group numbers for the FL list.
-* XFR NS's now include the origin server.
+* [XFR](../commands/xfr.md) NS's now include the server it was sent from.
 * Official Client: Error codes 602, 603, 911 (since removal in Client Version 3.0) are implemented.
   Error code 604 is no longer handled since Client Version 2.0.
 * Official website's `whatsnew.asp` page has been updated.
 * Official Client: New service URLs for some features.
 
-Client-server communication example:
+# Client-server communication example
 ```
 C: VER 1 MSNP7 MSNP6 MSNP5 MSNP4 CVR0
 S: VER 1 MSNP7
@@ -110,4 +115,4 @@ Client disconnects from server
 ```
 S: OUT
 ```
-Server disconnects client
+Server disconnects client

docs/versions/msnp8.md

@@ -1,6 +1,10 @@
+# Introduction
+
 MSNP8 is the seventh released version of the Mobile Status Notification Protocol.
 It was introduced officially in Client Version 5.0.0537.
 
+# Command information
+
 *No commands for any service were known to be introduced in this version*
 
 *No error codes were known to be introduced in this version*
@@ -9,7 +13,8 @@ The following commands were removed in this version:
 * INF (automatic disconnection)
 * FND (`502` by July 2003, see Known changes for client details.)
 
-Known changes (from [MSNP7](msnp7.md)):
+# Known changes
+(from [MSNP7](msnp7.md)):
 * Being the first protocol split,
   all released clients that support MSNP8 do not support any previous versions.
 * Login process now VER-CVR-USR instead of VER-INF-USR.
@@ -37,9 +42,8 @@ Known changes (from [MSNP7](msnp7.md)):
   The URL is gathered from `svcs.microsoft.com`.
   `abch_config.asp` provides an XML document with a `<abchconfig>` element.
   It likely has a `<url>` child element containing the URL of the ABCH service.
-  
 
-Client-server communication example:
+# Client-server communication example
 ```
 C: VER 1 MSNP8 CVR0
 S: VER 1 MSNP8

docs/versions/msnp9.md

@@ -1,6 +1,10 @@
+# Introduction
+
 MSNP9 is the eighth released version of the Mobile Status Notification Protocol.
 It was introduced officially in Client Version 6.0.0312.
 
+# Command information
+
 It introduces the notification service commands:
 * PGD
 
@@ -12,15 +16,17 @@ It introduces the error codes:
 The following commands were removed in this version:
 * PAG (returns 715)
 
-Known changes (from [MSNP8](msnp8.md)):
+# Known changes
+(from [MSNP8](msnp8.md)):
 * ILN, NLN, CHG: Added a MSNObject parameter.
   Now you can tell other clients about image data associated with your account.
 * QNG: Added a "next ping" time (in seconds) parameter
-* Switchboard-MSG: Acknoledgement type D added
+* Switchboard MSG: Acknowledgement type D added
 * Official Client: Error 603 is handled again after being removed in Client Version 5.0.
   Error code 711 is no longer handled after being implemented in Client Version 5.0.
 * Official Client: Supports the Messenger Config XML service, replacing `svcs.microsoft.com`.
-Client-server communication example:
+
+# Client-server communication example
 ```
 C: VER 1 MSNP9 MSNP8 CVR0
 S: VER 1 MSNP9

package-lock.json

@@ -680,8 +680,8 @@
       }
     },
     "node_modules/yiki": {
-      "version": "0.1.2",
+      "version": "0.1.3",
-      "resolved": "git+https://git.kevinthe.horse/yellows111/yiki.git#4e65d573b281eca56fca10910ea026785152a6b5",
+      "resolved": "git+https://git.kevinthe.horse/yellows111/yiki.git#8736d49e527cd9127fbf4d78ea7b648f5af5da16",
       "license": "MIT",
       "dependencies": {
         "@liquify/prettify": "^0.5.5-beta.1",