Reflect recent config changes to the doc

docs/operate/configuration.mdx

@@ -44,7 +44,7 @@ For example, to override the `admin.bind-address`, the corresponding environment
 
 If you want to generate a configuration file that includes values loaded from your environment variables or overrides applied to `restate-server` command-line, you can add `--dump-config` to dump the default TOML config with overrides applied:
 ```console
-restate-binary --cluster-name=mycluster --dump-config
+restate-server --cluster-name=mycluster --dump-config
 ```
 Example output:
 ```toml
@@ -57,7 +57,7 @@ cluster-name = "mycluster"
 ...
 ```
 
-At any time, you ask restate daemon to print the loaded configuration to the log by sending a `SIGUSR1` to the server process. This prints a dump of the live configuration to `INFO` level.
+At any time, you ask restate daemon to print the loaded configuration to the log by sending a `SIGUSR1` to the server process. This prints a dump of the live configuration to standard error.
 
 For instance on Mac/Linux, you can find the PID of restate-server by running:
 ```console
@@ -68,7 +68,7 @@ Then send the signal to the process ID returned from `pgrep`'s output:
 ```shell
 kill -USR1 994921
 ```
-Observe the log output of the server for a dump of the configuration file contents.
+Observe the output of the server for a dump of the configuration file contents.
 
 
 ## Default configuration

docs/operate/monitoring/logging.md

@@ -31,7 +31,7 @@ The following components are producing relevant logs:
 * `restate_admin`: The component responsible for holding the metadata information and executing service discovery
 * `restate_invoker`: The component interacting with deployed service deployments
 * `restate_worker::partition::state_machine`: The state machine effects
-* `restate_storage`: Restate storage layer
+* `restate_partition_store`: Restate partition storage layer
 * `restate_bifrost`: Restate durable log layer
 * `hyper`: The HTTP library
 
@@ -51,4 +51,4 @@ We recommend to set up logging to a more verbose filter, and use the `pretty` fo
 
 * `info,restate_ingress_http=trace,restate_invoker=trace,restate=debug,hyper=debug` for network related issues
 * `info,restate_worker::partition::effects=debug` to get insights on the state machine effects
-* `info,restate_meta=trace` to check service discovery and registration
+* `info,restate_admin=trace` to check service discovery and registration