diff --git a/docs/index.md b/docs/index.md
index 38c0171b..2cd23165 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -5,10 +5,9 @@
 `streaming_form_data` provides a Python parser for parsing `multipart/form-data` input
 chunks (the most commonly used encoding when submitting data through HTML forms).
 
-Chunk size is determined by the API user, but currently there are no
-restrictions on what the chunk size should be, since the parser works
-byte-by-byte (which means that passing the entire input as a single chunk should
-also work).
+Chunk size is determined by the API user, but currently there are no restrictions on
+what the chunk size should be, since the parser works byte-by-byte (which means that
+passing the entire input as a single chunk should also work).
 
 ## Installation
 
@@ -19,86 +18,85 @@ $ pip install streaming_form_data
 The core parser is written in `Cython`, which is a superset of Python that compiles the
 input down to a C extension which can then be imported in normal Python code.
 
-The compiled C parser code is included in the PyPI package, hence the
-installation requires a working C compiler.
+The PyPI package includes a pre-built binary wheel for Windows, macOS and Linux. If
+you'd like to install from the source code, the compiled C parser code is also included
+in the PyPI package.
 
 ## Usage
 
 ```python
->>> from streaming_form_data import StreamingFormDataParser
->>> from streaming_form_data.targets import ValueTarget, FileTarget, NullTarget
->>>
->>> headers = {'Content-Type': 'multipart/form-data; boundary=boundary'}
->>>
->>> parser = StreamingFormDataParser(headers=headers)
->>>
->>> parser.register('name', ValueTarget())
->>> parser.register('file', FileTarget('/tmp/file.txt'))
->>> parser.register('discard-me', NullTarget())
->>>
->>> for chunk in request.body:
-...     parser.data_received(chunk)
-...
->>>
+from streaming_form_data import StreamingFormDataParser
+from streaming_form_data.targets import ValueTarget, FileTarget, NullTarget
+
+headers = {'Content-Type': 'multipart/form-data; boundary=boundary'}
+
+parser = StreamingFormDataParser(headers=headers)
+
+parser.register('name', ValueTarget())
+parser.register('file', FileTarget('/tmp/file.txt'))
+parser.register('discard', NullTarget())
+
+for chunk in request.body:
+     parser.data_received(chunk)
 ```
 
-Usage can broadly be split into three stages.
+Usage is split into three stages.
 
 ### 1. Initialization
 
-The `StreamingFormDataParser` class expects a dictionary of HTTP request headers when
-being instantiated. These headers are used to determine the input `Content-Type` and a
-few other metadata.
+The `StreamingFormDataParser` class expects a dictionary of HTTP request headers for
+instantiation. These headers are used to determine the input `Content-Type` and a few
+other metadata.
 
 Optionally, you can enable strict mode in the parser by setting the `strict` keyword
-argument to `True`. In strict mode, the parser throws `UnexpectedPartException` if it
-starts to parse a field whose name has not been registered. When not in strict mode,
+argument to `True`. In strict mode, the parser throws the `UnexpectedPartException` if
+it starts to parse a field whose name has not been registered. When not in strict mode,
 unexpected parts are silently ignored.
 
 ### 2. Input Registration
 
-HTML forms typically have multiple fields. For instance, a form could have a text input
-field called `name` and a file input field called `file`.
+HTML forms can have multiple fields. For instance, a form could have a text input field
+called `name` and a file input field called `file`.
 
-This needs to be communicated to the parser using the `parser.register` function. This
-function expects two arguments - the name of the input field, and the associated
-`Target` class (which determines how the input should be handled).
+This needs to be communicated to the parser using the `parser.register` method. This
+method expects two arguments - the name of the input field and the associated `Target`
+class (which determines how the input should be handled).
 
 For instance, if you want to store the contents of the `name` field in an in-memory
 variable, and the `file` field in a file on disk, you can tell this to the parser as
 follows.
 
 ```python
->>> name_target = ValueTarget()
->>> file_target = FileTarget('/tmp/file.dat')
->>>
->>> parser.register('name', name_target)
->>> parser.register('file', file_target)
+name_target = ValueTarget()
+file_target = FileTarget('/tmp/file.dat')
+
+parser.register('name', name_target)
+parser.register('file', file_target)
 ```
 
-Registering multiple targets is also supported.
+Registering multiple targets for the same field is also supported.
 
 ```python
->>> name_target = ValueTarget()
->>> sha256_target = SHA256Target()
->>>
->>> parser.register('file', name_target)
->>> parser.register('file', sha256_target)
+name_target = ValueTarget()
+sha256_target = SHA256Target()
+
+parser.register('file', name_target)
+parser.register('file', sha256_target)
 ```
 
-In this case, the contents of the `file` field would be streamed to both the
-`ValueTarget` as well as the `SHA256Target`.
+In this case, the contents of the `file` field would be streamed to both `ValueTarget`
+and `SHA256Target`.
 
 ### 3. Streaming data
 
-At this stage the parser has everything it needs to be able to work. Depending
-on what web framework you're using, just pass the actual HTTP request body to
-the parser, either one chunk at a time or the complete thing at once.
+At this stage the parser has everything it needs to be able to work. Depending on what
+web framework you're using, you can send the actual HTTP request body to the parser,
+either one chunk at a time or the whole thing at once.
 
 ```python
->> chunk = read_next_chunk() # depends on your web framework of choice
->>
->> parser.data_received(chunk)
+chunk = read_next_chunk() # depends on your web framework of choice
+
+parser.data_received(chunk)
 ```
 
 ## API
@@ -120,23 +118,24 @@ should be used. These target classes ultimately determine what to do with the da
 `ValueTarget` objects hold the input in memory.
 
 ```python
->>> target = ValueTarget()
+target = ValueTarget()
 ```
 
 #### `FileTarget`
 
-`FileTarget` objects stream the contents to a file on-disk.
+`FileTarget` objects stream the contents to a file on disk.
 
 ```python
->>> target = FileTarget('/tmp/file.txt')
+target = FileTarget('/tmp/file.txt')
 ```
 
 #### `DirectoryTarget`
 
-`DirectoryTarget` objects stream the contents to a directory on-disk.
+`DirectoryTarget` objects stream the contents to a directory on disk; the filename will
+be picked from the `Content-Disposition` header.
 
 ```python
->>> target = DirectoryTarget('/tmp/uploads/')
+target = DirectoryTarget('/tmp/uploads/')
 ```
 
 #### `SHA256Target`
@@ -145,7 +144,7 @@ should be used. These target classes ultimately determine what to do with the da
 in memory.
 
 ```python
->>> target = SHA256Target()
+target = SHA256Target()
 ```
 
 #### `NullTarget`
@@ -153,7 +152,7 @@ in memory.
 `NullTarget` objects discard the input completely.
 
 ```python
->>> target = NullTarget()
+target = NullTarget()
 ```
 
 #### `S3Target`
@@ -161,7 +160,7 @@ in memory.
 `S3Target` objects stream the contents of a file to an S3 bucket.
 
 ```python
->>> target = S3Target("s3://<bucket>/path/to/key", "wb")
+target = S3Target("s3://<bucket>/path/to/key", "wb")
 ```
 
 #### `GCSTarget`
@@ -169,7 +168,7 @@ in memory.
 `GCSTarget` objects stream the contents of a file to a Google Cloud Storage bucket.
 
 ```python
->>> target = GCSTarget("gs://<bucket>/path/to/key", "wb")
+target = GCSTarget("gs://<bucket>/path/to/key", "wb")
 ```
 
 #### `CSVTarget`
@@ -177,7 +176,7 @@ in memory.
 `CSVTarget` objects process and release CSV lines in chunks.
 
 ```python
->>> target = CSVTarget()
+target = CSVTarget()
 ```
 
 #### `ListTarget`
@@ -185,42 +184,69 @@ in memory.
 `ListTarget` objects store the input in an in-memory list of bytes.
 
 ```python
->>> target = ListTarget()
+target = ListTarget()
 ```
 
+#### `MultipleTargets`
+
+`MultipleTargets` objects allow you to handle the case when a user uploads multiple
+files for the same field. The class expects a single `next_target` parameter which
+should be a `Callable` that returns another `Target` instance every time it's called.
+
+Here's an example snippet:
+
+```python
+from streaming_form_data.targets import FileTarget
+
+class _next_target:
+    def __init__(self):
+        self._index = 0
+
+    def __call__(self):
+        return FileTarget(filename=f"{self._index}.dat")
+
+# next_target is a callable that returns a new FileTarget every time it's called
+next_target = _next_target()
+
+target = MultipleTargets(next_target)
+```
+
+With this in place, every time the parser sees a new part with the name `files`, it will
+instantiate a new `FileTarget` with a different filename and start streaming the data
+into this new target.
+
 #### Custom `Target` classes
 
 It's possible to define custom targets for your specific use case by inheriting the
 `streaming_form_data.targets.BaseTarget` class and overriding the `on_data_received`
-function.
+method.
 
 ```python
->>> from streaming_form_data.targets import BaseTarget
->>>
->>> class CustomTarget(BaseTarget):
-...     def on_data_received(self, chunk):
-...         do_something(chunk)
+from streaming_form_data.targets import BaseTarget
+
+class CustomTarget(BaseTarget):
+     def on_data_received(self, chunk):
+         do_something(chunk)
 ```
 
 If the `Content-Disposition` header included the `filename` directive, this value will
-be available as the `self.multipart_filename` attribute in `Target` classes.
-
+be available as the `self.multipart_filename` attribute in `Target` instances.
 Similarly, if the `Content-Type` header is available for the uploaded files, this value
 will be available as the `self.multipart_content_type` attribute in `Target` classes.
 
 ### `Validator` classes
 
-`Target` classes accept a `validator` callable when being instantiated. Every time
+`Target` classes accept a `validator` callable at instantiation time. Every time
 `data_received` is called with a given `chunk`, the target runs this `chunk` through the
 given callable.
 
-This is useful for performing certain validation tasks like making sure the input size
-is not exceeding a certain value. This is shown in the following code snippet.
+This is useful for performing specific validation tasks like making sure the input size
+is not exceeding a certain value. For instance,
 
 ```python
->>> from streaming_form_data.targets import ValueTarget
->>>
->>> target = ValueTarget(validator=MaxSizeValidator(100))
+from streaming_form_data.targets import ValueTarget
+
+target = ValueTarget(validator=MaxSizeValidator(100))
 ```
 
 ### Exceptions
@@ -237,11 +263,11 @@ unexpected part. It contains `part_name` attribute to check the name of the unex
 part. In can only be raised from `data_received`.
 
 ```python
->>> try:
->>>    parser.data_received(chunk)
->>> except streaming_form_data.parser.UnexpectedPartException as e:
->>>    print(e.part_name)
->>>    raise
+try:
+   parser.data_received(chunk)
+except streaming_form_data.parser.UnexpectedPartException as e:
+   print(e.part_name)
+   raise
 ```
 
 ## Examples