doc: Add note that sorting in collections is no hard rule

Signed-off-by: Matthias Beyer <mail@beyermatthias.de>

1 files changed, 6 insertions, 4 deletions

diff --git a/doc/src/02000-store.md b/doc/src/02000-store.md
index aab16453..07334cea 100644
--- a/doc/src/02000-store.md
+++ b/doc/src/02000-store.md
@@ -103,16 +103,16 @@ necessary.
 We name the path to a file in the store "Store id" or "Storepath" and we often
 refer to it by using the store location as root.
 So if the store exists in `/home/user/store/`, a file with the storepath
-`/example.file` is (on the filesystem) located at
+`example.file` is (on the filesystem) located at
 `/home/user/store/example.file`.
 
 By convention, each `libimagentry<name>` and `libimag<name>` module stores its
-entries in in `/<name>/`.
+entries in in `<name>/`.
 
 So, the pattern for the storepath is
 
 ```
-/<module name>/<optional sub-folders>/<file name>
+<module name>/<optional sub-folders>/<file name>
 ```
 
 Any number of subdirectories may be used, so creating folder hierarchies is
@@ -120,9 +120,11 @@ possible and valid.
 A file "example" for a module "module" could be stored in sub-folders like this:
 
 ```
-/module/some/sub/folder/example
+module/some/sub/folder/example
 ```
 
+The above is not enforced or a strict rule, but rather a "rule of thumb".
+
 ## Backends {#sec:thestore:backends}
 
 The store itself also has a backend. This backend is the "filesystem