docs(config): Make example in guides/level-up/managing-complex-config…

…s work with Vector 0.18 (#10168)

* docs: For sources in tcp/udp mode, the path param does not make sense

It is not invalid as of 0.18 but should be. At least lets stop giving
such examples.

* docs: Fix typo

* docs: Fix example config: encoding.codec is required now for console sink

website/content/en/guides/level-up/managing-complex-configs.md

@@ -181,7 +181,7 @@ individual files, each with its own unit tests.
 
 ## Splitting Configs
 
-If your components start to by used in multiple configuration files, having a
+If your components start to be used in multiple configuration files, having a
 dedicated place to define them can become interesting.
 
 With Vector you can define a component configuration inside a component type folder.
@@ -194,7 +194,6 @@ type = "syslog"
 address = "0.0.0.0:514"
 max_length = 42000
 mode = "tcp"
-path = "/path/to/socket"
 
 [transforms.change_fields]
 type = "remap"
@@ -207,6 +206,7 @@ source = """
 type = "console"
 inputs = ["change_fields"]
 target = "stdout"
+encoding.codec = "json"
 ```
 
 We can extract the `syslog` source in the file `/etc/vector/sources/syslog.toml`
@@ -216,7 +216,6 @@ type = "syslog"
 address = "0.0.0.0:514"
 max_length = 42000
 mode = "tcp"
-path = "/path/to/socket"
 ```
 
 The `change_fields` transform in the file `/etc/vector/transforms/change_fields.toml`