Remove refs to 'data.bin'

Author: ohsayan

docs/9.persistence.md

@@ -9,7 +9,7 @@ Skytable supports the persistent storage of data, which is an inherently obvious
 
 As soon as you start Skytable, it will look for a `PRELOAD` file in the data directory. If it
 isn't found — the server would expect this to be a new instance and will create the
-required files for you. Skytable uses a disk storage format called **Snapstore** (version `1A`)
+required files for you. Skytable uses a disk storage format called **Cyanstore** (version `1A`)
 for storing your data and all files are encoded/decoded in compliance with this format.
 
 Once you terminate the daemon, it will flush all data to disk. All writes are `fsync`ed by the time
@@ -29,7 +29,7 @@ can be configured and used by users.
 
 Skytable supports automated saving of data in the background, via `BGSAVE`. `BGSAVE`, runs every two minutes to flush all the data in the in-memory table onto disk, unless customized through the [configuration file](config-files/#an-example-configuration). BGSAVE is enabled by default and we don't recommend disabling it until you're sure that
 your hardware will never fail; it is likely that this will never be the case. First BGSAVE will create a temporary
-file and then flush the current in-memory table onto disk. It will then replace the old `data.bin` file. The daemon automatically `fsync`s after every successful write (whether to the buffers or
+file and then flush the current in-memory table onto disk. The daemon automatically `fsync`s after every successful write (whether to the buffers or
 to the actual disk).
 
 ### Reliability of BGSAVE