docs: narrow quickstart changes to setup and configuration paths

Author: JinchengCao

website/content/en/docs/setup/quickstart.md

@@ -64,10 +64,9 @@ mkdir vector-quickstart
 cd vector-quickstart
 ```
 
-Run all remaining commands from this directory. Copy and run the entire command below, including the final `YAML` line, to create `vector.yaml`:
+Let's create a configuration file called `vector.yaml`:
 
-```shell
-cat > vector.yaml <<'YAML'
+```yaml filename="vector.yaml"
 sources:
   in:
     type: "stdin"
@@ -79,7 +78,6 @@ sinks:
     type: "console"
     encoding:
       codec: "text"
-YAML
 ```
 
 Each component has a unique id and is prefixed with the type of the component, for example `sources` for a source. Our first component, `sources.in`, uses the [`stdin` source][stdin], which tells Vector to receive data over stdin and is given the ID `in`.
@@ -90,7 +88,7 @@ The `inputs` option of the `sinks.out` component tells Vector where this sink's
 
 ## Hello world!
 
-That's it for our first config. Now let's pipe an event through it. Choose the tab for your installation method:
+That's it for our first config. Now let's pipe an event through it:
 
 {{< tabs default="Local installation" >}}
 {{< tab title="Local installation" >}}
@@ -119,16 +117,16 @@ The event we've just sent is received by our `sources.in` component, then sent o
 
 ```shell
 ... some logs ...
-Hello world!
+Hello World!
 ```
 
 {{< info title="JSON encoding" >}}
-To see the event as JSON, change `codec: "text"` to `codec: "json"` under `encoding` in the sink configuration and run the command again.
+If you want to see something cool, try setting `encoding.codec = "json"` in the sink config.
 {{< /info >}}
 
 ## Hello Syslog!
 
-Next, let's collect and process generated Syslog events. Open the same `vector.yaml` file in your text editor, replace its entire contents with the following configuration, and save the file:
+Echoing events into the console isn't terribly exciting. Let's see what we can do with some real observability data by collecting and processing Syslog events. To do that, we'll add two new components to our configuration file. Here's our updated `vector.yaml` configuration file:
 
 ```yaml filename="vector.yaml"
 sources:
@@ -157,9 +155,9 @@ sinks:
 
 The first component uses the [`demo_logs` source][demo_logs], which creates sample log data that enables you to simulate different types of events in various formats.
 
-{{< info >}}
-Generated logs let you try this pipeline without connecting to an external log source.
-{{< /info >}}
+{{< warning >}}
+Wait, I thought you said "real" observability data? We choose generated data here because it's hard for us to know which platform you're trying Vector on. That means it's also hard to document a single way for everyone to get data into Vector.
+{{< /warning >}}
 
 The second component is a transform called [`remap`][remap]. The `remap` transform is at the heart of what makes Vector so powerful for processing observability data. The transform exposes a simple language called [Vector Remap Language][vrl] that allows you to parse, manipulate, and decorate your event data as it passes through Vector. Using `remap`, you can turn static events into informational
 data that can help you ask and answer questions about your environment's state.
@@ -176,7 +174,7 @@ We support parsing a variety of logging formats. Of course, if you have an event
 
 Lastly, we've updated the ID of our sink component to `emit_syslog`, updated the `inputs` option to process events generated by the `remap_syslog` transform, and specified that we want to emit events in JSON-format.
 
-Let's re-run Vector from the same directory, choosing the tab for your installation method. This time we don't need to echo any data to it. It'll process
+Let's re-run Vector. This time we don't need to echo any data to it; just run in on the command line. It'll process
 100 lines of generated Syslog data, emit the processed data as JSON, and exit:
 
 {{< tabs default="Local installation" >}}
@@ -212,6 +210,7 @@ We're just scratching the surface in this post. To get your hands dirty with Vec
 
 * All of Vector's [sources][sources], [transforms][transforms], and [sinks][sinks].
 * The [Vector Remap Language][vrl], the heart of data processing in Vector.
+* More details on [component configuration][config] in Vector.
 * Finally, [deploying Vector][deployment] to launch Vector in your production environment.
 
 [components]: /components