diff --git a/README.md b/README.md
index de0f2c7b..406cfe41 100644
--- a/README.md
+++ b/README.md
@@ -230,7 +230,7 @@ Most parsers load all of the data from STDIN, parse it, then output the entire J
 
 > Note: Streaming parsers cannot be used with the "magic" syntax
 
-**Ignoring Errors**
+####Ignoring Errors
 
 You may want to ignore parsing errors when using streaming parsers since these may be used in long-lived processing pipelines and errors can break the pipe. To ignore parsing errors, use the `-q` cli option or the `quiet=True` argument with the `parse()` function. This will add a `_meta` object to the JSON output with a `success` attribute. If `success` is `true`, then there were no issues parsing the line. If `success` is `false`, then a parsing issue was found and `error` and `line` fields will be added to include a short error description and the contents of the unparsable line, respectively:
 
@@ -254,7 +254,7 @@ Unsuccessfully parsed line with `-q` option:
 }
 ```
 
-**Unbuffering Output**
+####Unbuffering Output
 
 Most operating systems will buffer output that is being piped from process to process. The buffer is usually around 4KB. When viewing the output in the terminal the OS buffer is not engaged so output is immediately displayed on the screen. When piping multiple processes together, though, it may seem as if the output is hanging when the input data is very slow (e.g. `ping`):
 ```
@@ -268,7 +268,22 @@ $ ping 1.1.1.1 | jc --ping-s -u | jq
 {"type":"reply","pattern":null,"timestamp":null,"bytes":"64","response_ip":"1.1.1.1","icmp_seq":"2","ttl":"128","time_ms":"26.8","duplicate":false}
 ...
 ```
-> Note: Unbuffered output can be slower for faster data streams.
+> Note: Unbuffered output can be slower for large data streams.
+
+####Using Streaming Parsers as Python Modules
+
+Streaming parsers accept any iterable object and return a generator iterator object allowing lazy processing of the data. The input data should iterate on lines of string data. Examples of good input data are `sys.stdin` or `str.splitlines()`.
+
+To use the generator object in your code, simply loop through it:
+
+```
+import json
+import jc.parsers.ls_s
+
+result = jc.parsers.ls_s.parse(ls_command_output.splitlines())
+for item in result:
+    item_dict = json.loads(item)
+```
 
 ### Custom Parsers
 Custom local parser plugins may be placed in a `jc/jcparsers` folder in your local **"App data directory"**:
diff --git a/templates/readme_template b/templates/readme_template
index 94af7557..0f8e87b1 100644
--- a/templates/readme_template
+++ b/templates/readme_template
@@ -153,7 +153,7 @@ Most parsers load all of the data from STDIN, parse it, then output the entire J
 
 > Note: Streaming parsers cannot be used with the "magic" syntax
 
-**Ignoring Errors**
+####Ignoring Errors
 
 You may want to ignore parsing errors when using streaming parsers since these may be used in long-lived processing pipelines and errors can break the pipe. To ignore parsing errors, use the `-q` cli option or the `quiet=True` argument with the `parse()` function. This will add a `_meta` object to the JSON output with a `success` attribute. If `success` is `true`, then there were no issues parsing the line. If `success` is `false`, then a parsing issue was found and `error` and `line` fields will be added to include a short error description and the contents of the unparsable line, respectively:
 
@@ -177,7 +177,7 @@ Unsuccessfully parsed line with `-q` option:
 }
 ```
 
-**Unbuffering Output**
+####Unbuffering Output
 
 Most operating systems will buffer output that is being piped from process to process. The buffer is usually around 4KB. When viewing the output in the terminal the OS buffer is not engaged so output is immediately displayed on the screen. When piping multiple processes together, though, it may seem as if the output is hanging when the input data is very slow (e.g. `ping`):
 ```
@@ -191,7 +191,22 @@ $ ping 1.1.1.1 | jc --ping-s -u | jq
 {"type":"reply","pattern":null,"timestamp":null,"bytes":"64","response_ip":"1.1.1.1","icmp_seq":"2","ttl":"128","time_ms":"26.8","duplicate":false}
 ...
 ```
-> Note: Unbuffered output can be slower for faster data streams.
+> Note: Unbuffered output can be slower for large data streams.
+
+####Using Streaming Parsers as Python Modules
+
+Streaming parsers accept any iterable object and return a generator iterator object allowing lazy processing of the data. The input data should iterate on lines of string data. Examples of good input data are `sys.stdin` or `str.splitlines()`.
+
+To use the generator object in your code, simply loop through it:
+
+```
+import json
+import jc.parsers.ls_s
+
+result = jc.parsers.ls_s.parse(ls_command_output.splitlines())
+for item in result:
+    item_dict = json.loads(item)
+```
 
 ### Custom Parsers
 Custom local parser plugins may be placed in a `jc/jcparsers` folder in your local **"App data directory"**: