fix typo: remove redundant 'to' in configuration instructions

docs/operators/how-to/configure-store.md

@@ -35,7 +35,7 @@ There is a set of configuration options to customize the waku store protocol's m
   + The time retention policy,`time:<duration-in-seconds>` (e.g., `time:14400`)
   + The capacity retention policy,`capacity:<messages-count>` (e.g, `capacity:25000`)
   + The size retention policy,`size:<size-in-gb-mb>` (e.g, `size:25Gb`)
-  + To disable the retention policy, explicitly, set this option to to `""`, an empty string.
+  + To disable the retention policy, explicitly, set this option to `""`, an empty string.
 * `--store-message-db-url`: The message store database url option controls the message storage engine. This option follows the [_SQLAlchemy_ database URL format](https://docs.sqlalchemy.org/en/14/core/engines.html#database-urls).
 
   + SQLite engine: The only database engine supported by the nwaku node. The database URL has this shape: `sqlite://<database-file-path>`. If the `<database-file-path>` is not an absolute path (preceded by a `/` character), the file will be created in the current working directory. The SQLite engine also supports to select a non-persistent in-memory database by setting the `<database-file-path>` to `:memory:`.
@@ -55,4 +55,4 @@ wakunode2 \
 ### How much resources should I allocate?
 
 Currently store service nodes use, by default, a message store backed by an in-disk SQLite database. Most Waku messages average a size of 1KB - 2KB, implying a minimum memory requirement of at least ~250MB
-for a typical store capacity of 100k messages. Note, however, that the allowable maximum size for Waku messages is up to 1MB.
+for a typical store capacity of 100k messages. Note, however, that the allowable maximum size for Waku messages is up to 1MB.