Update readme

Author: terehov

docs/README.md

@@ -27,7 +27,7 @@
 🦸 **Custom pluggable loggers**<br>
 💅 **Object and error interpolation**<br>
 🤓 **Stack trace and pretty errors**<br>
-👨‍👧‍👦 **Sub logger with inheritance**<br>
+👨‍👧‍👦 **Sub-logger with inheritance**<br>
 🙊 **Mask/hide secrets and keys**<br>
 📦 **CJS & ESM with tree shaking support**<br>
 ✍️ **Well documented and tested**<br>
@@ -181,7 +181,7 @@ logger.fatal(new Error("I am a pretty Error with a stacktrace."));
 - **Object/JSON highlighting:** Nicely prints out objects
 - **Instance Name**: _(Server-side only)_ Logs capture instance name (default host name) making it easy to distinguish logs coming from different instances
 - **Named Logger:** Logger can be named (e.g. useful for packages/modules and monorepos)
-- **Sub Logger with inheritance:** Powerful sub-loggers with settings inheritance, also at runtime
+- **Sub-logger with inheritance:** Powerful sub-loggers with settings inheritance, also at runtime
 - **Secrets masking:** Prevent passwords and secrets from sneaking into log files by masking them
 - **Short paths:** Paths are relative to the root of the application folder
 - **Prefixes:** Prefix log messages and bequeath prefixes to child loggers
@@ -309,7 +309,7 @@ const hiddenLogger = new Logger({type: "hidden"});
 
 Each logger has an optional name.
 You can find the name of the logger responsible for a log inside the `Meta`-object or printed in `pretty` mode.
-Names get also inherited to sub loggers and can be found inside the `Meta`-object `parentNames` as well as printed out with a separator (e.g. `:`) in `pretty` mode.
+Names get also inherited to sub-loggers and can be found inside the `Meta`-object `parentNames` as well as printed out with a separator (e.g. `:`) in `pretty` mode.
 
 Simple name example:
 ```typescript
@@ -462,7 +462,7 @@ There are multiple ways of masking secrets, before they get exposed:
 
 #### Prefixing logs
 Prefix every log message with an array of additional attributes.<br>
-Prefixes propagate to sub loggers and can help to follow a chain of promises.<br>
+Prefixes propagate to sub-loggers and can help to follow a chain of promises.<br>
 In addition to <a href="https://nodejs.org/api/async_hooks.html#async_hooks_class_asynclocalstorage" target="_blank">`AsyncLocalStorage`</a>, prefixes can help further distinguish different parts of a request.
 
 > **Hint:** A good example could be a GraphQL request, that by design could consist of multiple queries and/or mutations.
@@ -679,7 +679,7 @@ When debugging it can be quite handy to be able to group all logs based on a uni
 
 Some providers (e.g. `Heroku`) already set a `X-Request-ID` header, which we are going to use or fallback to a short ID generated by <a href="https://www.npmjs.com/package/nanoid" target="_blank">`nanoid`</a>.
 
-**In this example every subsequent logger is a sub logger of the main logger and thus inherits all of its settings making `requestId` available throughout the entire application without any further ado.**
+**In this example every subsequent logger is a sub-logger of the main logger and thus inherits all of its settings making `requestId` available throughout the entire application without any further ado.**
 
 `tslog` works with any API framework (like `Express`, `Koa`, `Hapi` and so on), but in this example we are using `Koa`.
 ```typescript
@@ -722,7 +722,7 @@ Some providers (e.g. `Heroku`) already set a `X-Request-ID` header, which we are
     // log request
     logger.silly({ originalUrl: ctx.originalUrl, status: ctx.response.status, message: ctx.response.message });
 
-    // also works with a sub logger
+    // also works with a sub-logger
     const subLogger = logger.getSubLogger();
     subLogger.info("Log containing requestId"); // <-- will contain a requestId