diff --git a/synapse/storage/README.md b/synapse/storage/README.md
deleted file mode 100644
index 567ae785a..000000000
--- a/synapse/storage/README.md
+++ /dev/null
@@ -1,13 +0,0 @@
-Storage Layer
-=============
-
-The storage layer is split up into multiple parts to allow Synapse to run
-against different configurations of databases (e.g. single or multiple
-databases). The `data_stores` are classes that talk directly to a single
-database and have associated schemas, background updates, etc. On top of those
-there are (or will be) classes that provide high level interfaces that combine
-calls to multiple `data_stores`.
-
-There are also schemas that get applied to every database, regardless of the
-data stores associated with them (e.g. the schema version tables), which are
-stored in `synapse.storage.schema`.
diff --git a/synapse/storage/__init__.py b/synapse/storage/__init__.py
index 2f29c4a11..a249ecd21 100644
--- a/synapse/storage/__init__.py
+++ b/synapse/storage/__init__.py
@@ -14,6 +14,18 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 
+"""
+The storage layer is split up into multiple parts to allow Synapse to run
+against different configurations of databases (e.g. single or multiple
+databases). The `data_stores` are classes that talk directly to a single
+database and have associated schemas, background updates, etc. On top of those
+there are (or will be) classes that provide high level interfaces that combine
+calls to multiple `data_stores`.
+
+There are also schemas that get applied to every database, regardless of the
+data stores associated with them (e.g. the schema version tables), which are
+stored in `synapse.storage.schema`.
+"""
 
 from synapse.storage.data_stores.main import DataStore  # noqa: F401