diff --git a/persistent_storage.md b/persistent_storage.md
index 3de132a..013f7c5 100644
--- a/persistent_storage.md
+++ b/persistent_storage.md
@@ -36,4 +36,14 @@ The output may look like this:

The takeaway from the screenshot above is this is another way of looking at the storage and how it's been assigned to the URLs.
- You can see the grouping of multiple URLs sharing the same storage endpoint is also listed here.
-- It will identify the current amount of disk storage you have in use for the given plugin as well
\ No newline at end of file
+- It will identify the current amount of disk storage you have in use for the given plugin as well
+- Any plugin that does not even utilize peristent storage at all, will not show up in this list. In the screenshot before this one you will see `dbus://` where it is not identified `storage` results.
+
+The possible disk states are:
+- `unused`: The plugin is not occupying any persistent storage on disk
+- `stale`: At one pint a plugin exists that wrote to a location that is no longer being referenced.
+ - You can clear these entries by simply typing:
+ ```bash
+ apprise storage clean
+ ```
+- `active`: The plugin contains data written into it's cached location.