26.2.23 stuff

Author: CamDavidsonPilon

developer-guide/09-Storage and the filesystem/01-data-stores/local_storage.md

@@ -12,21 +12,26 @@ Here's an example:
 from pioreactor.utils import local_intermittent_storage, local_peristant_storage
 
 
-with local_intermittent_storage("my_namespace2") as cache:
+with local_intermittent_storage("my_namespace") as cache:
     cache['key'] = "value"
     print(cache['key'])
 
+    cache.get("retrieval_key")
 
-with local_peristant_storage("my_namespace1") as cache:
+
+with local_peristant_storage("my_other_namespace") as cache:
     cache['key'] = "value"
+    print(cache['key'])
+
+    assert cache.get("retrieval_key") is None
 
 
 ```
 
-You can use `pio view-cache <name>` to view the contents of `<name>`, and `pio clear-cache <name> <key>` to clear contents.
+You can use `pio cache view <name>` to view the contents of `<name>`, and `pio cache purge <name> <key>` to clear contents.
 
 ### What's the difference between `local_intermittent_storage` and `local_peristent_storage`?
 
 `local_intermittent_storage` is data that won't, or shouldn't, exist after a reboot. For example: the state of GPIO pins. At a hardware level, this is reset after each reboot, and so should data associated with it. 
 
-Whereas `local_peristant_storage` is data that should exist between reboots. This is data like calibration data, or OD blank data.
+Whereas `local_peristant_storage` is data that should exist between reboots. This is data like some calibration data, or OD blank data.