diff --git a/docs/configuration/file-transfer-protocols.md b/docs/configuration/file-transfer-protocols.md
index fd21a938..2f7d48ac 100644
--- a/docs/configuration/file-transfer-protocols.md
+++ b/docs/configuration/file-transfer-protocols.md
@@ -2,10 +2,10 @@
 layout: page
 title: File Transfer Protocols
 ---
-ENiGMA½ currently relies on external executables for "legacy" file transfer protocols such as X, Y, and ZModem. The `fileTransferProtocols` section of `config.hjson` is used to override defaults, add new handlers, etc. Remember that ENiGMA½ also support modern web (HTTP/HTTPS) downloads!
+ENiGMA½ currently relies on external executable binaries for "legacy" file transfer protocols such as X, Y, and ZModem. Remember that ENiGMA½ also support modern web (HTTP/HTTPS) downloads!
 
 ## File Transfer Protocols
-File transfer protocols are managed via the `fileTransferProtocols` configuration block of `config.hjson`. Each entry defines an **external** protocol that can be used for uploads (recv), downloads (send), or both. Depending on the protocol and handler, batch receiving of files (uploads) may also be available.
+File transfer protocols are managed via the `fileTransferProtocols` configuration block of `config.hjson`. Each entry defines an **external** protocol handler that can be used for uploads (recv), downloads (send), or both. Depending on the protocol and handler, batch receiving of files (uploads) may also be available.
 
 ### Predefined File Transfer Protocols
 The following file transfer protocols are pre-configured in ENiGMA½ as of this writing. System operators may override or extend this list. PRs are welcome for pre-configured additions!
@@ -32,18 +32,21 @@ For protocols of type `external` the following members may be defined:
 * `recvArgsNonBatch`: Required if using `recvCmd` and supporting non-batch (single file) uploads; A placeholder of `{fileName}` may be supplied to indicate to the protocol what the uploaded file should be named (this will be collected from the user before the upload starts).
 * `escapeTelnet`: Optional; If set to `true`, escape all internal Telnet related codes such as IAC's. This option is required for external protocol handlers such as `sz` and `rz` that do not escape themselves.
 
+### Adding Your Own
+Take a look a the example below as well as [core/config.js](/core/config.js).
+
 #### Example File Transfer Protocol Configuration
 ```
 zmodem8kSexyz : {
-	name		: 'ZModem 8k (SEXYZ)',
-	type		: 'external',
-	sort		: 1,
-	external	: {
-		sendCmd				: 'sexyz',
-		sendArgs			: [ '-telnet', '-8', 'sz', '@{fileListPath}' ],
-		recvCmd				: 'sexyz',
-		recvArgs			: [ '-telnet', '-8', 'rz', '{uploadDir}' ],
-		recvArgsNonBatch	: [ '-telnet', '-8', 'rz', '{fileName}' ],
-	}
+    name		: 'ZModem 8k (SEXYZ)',
+    type		: 'external',
+    sort		: 1,
+    external	: {
+        sendCmd             : 'sexyz',
+        sendArgs            : [ '-telnet', '-8', 'sz', '@{fileListPath}' ],
+        recvCmd             : 'sexyz',
+        recvArgs            : [ '-telnet', '-8', 'rz', '{uploadDir}' ],
+        recvArgsNonBatch    : [ '-telnet', '-8', 'rz', '{fileName}' ],
+    }
 }
-```
\ No newline at end of file
+```