remove other unnecessary instances of $

Signed-off-by: Alexa Kreizinger <[email protected]>

Author: alexakreizinger

administration/monitoring.md

@@ -71,10 +71,10 @@ Start Fluent bit with the corresponding configuration chosen above:
 
 ```shell
 # For YAML configuration.
-$ ./bin/fluent-bit --config fluent-bit.yaml
+./bin/fluent-bit --config fluent-bit.yaml
 
 # For classic configuration.
-$ ./bin/fluent-bit --config fluent-bit.conf
+./bin/fluent-bit --config fluent-bit.conf
 ```
 
 Fluent Bit starts and generates output in your terminal:
@@ -282,7 +282,7 @@ The command prints a similar output like this:
 Query internal metrics in JSON format with the following command:
 
 ```shell
-$ curl -s http://127.0.0.1:2020/api/v1/metrics | jq
+curl -s http://127.0.0.1:2020/api/v1/metrics | jq
 ```
 
 The command prints a similar output like this:
@@ -312,7 +312,7 @@ The command prints a similar output like this:
 Query internal metrics in Prometheus Text 0.0.4 format:
 
 ```shell
-$ curl -s http://127.0.0.1:2020/api/v1/metrics/prometheus
+curl -s http://127.0.0.1:2020/api/v1/metrics/prometheus
 ```
 
 This command returns the same metrics in Prometheus format instead of JSON:
@@ -506,7 +506,7 @@ pipeline:
 Use the following command to call the health endpoint:
 
 ```shell
-$ curl -s http://127.0.0.1:2020/api/v1/health
+curl -s http://127.0.0.1:2020/api/v1/health
 ```
 
 With the example configuration, the health status is determined by the following equation:

development/msgpack-format.md

@@ -16,7 +16,7 @@ This section provides an overview of the specific types used by Fluent Bit withi
 Set up Fluent Bit to send in `msgpack` format to a specific port.
 
 ```bash
-$ docker run --rm -it --network=host fluent/fluent-bit /fluent-bit/bin/fluent-bit -i cpu -o tcp://127.0.0.1:5170 -p format=msgpack -v
+docker run --rm -it --network=host fluent/fluent-bit /fluent-bit/bin/fluent-bit -i cpu -o tcp://127.0.0.1:5170 -p format=msgpack -v
 
 ```
 

development/wasm-filter-plugins.md

@@ -35,9 +35,9 @@ Currently, Fluent Bit supports the following Wasm tool chains:
 As described in the general options in the [source installation](../installation/sources/build-and-install.md) guide, Wasm support is enabled by default. Compile Fluent Bit with Wasm support, for example:
 
 ```text
-$ cd build/
-$ cmake .. [-DFLB_WAMRC=On]
-$ make
+cd build/
+cmake .. [-DFLB_WAMRC=On]
+make
 ```
 
 To support AOT-compiled Wasm execution as filter plugins, build Fluent Bit with `-DFLB_WAMRC=On`.
@@ -65,7 +65,7 @@ The Fluent Bit Wasm filter assumes C ABI, also known as `wasm32-unknown-unknown`
 TinyGo and WASI SDK support Wasm target by default. When using Rust's `wasm32-unknown-unknown` target, you must install `wasm32-unknown-unknown` by using [rustup](https://rustup.rs/). Then, install the target components as follows:
 
 ```text
-$ rustup target add wasm32-unknown-unknown
+rustup target add wasm32-unknown-unknown
 ```
 
 ### Requirements of Wasm programs
@@ -228,13 +228,13 @@ To optimize Wasm program execution, there is the option of using `flb-wamrc`. Th
 This tool will be built when the `-DFLB_WAMRC=On` CMake option is specified and LLVM infrastructure is installed on the building box.
 
 ```shell
-$ flb-wamrc -o /path/to/built_wasm.aot /path/to/built_wasm.wasm
+flb-wamrc -o /path/to/built_wasm.aot /path/to/built_wasm.wasm
 ```
 
 For further optimizations to the specific CPU, such as Cortex-A57 series:
 
 ```text
-$ flb-wamrc --size-level=3 --target=aarch64v8 --cpu=cortex-a57 -o /path/to/built_wasm.aot /path/to/built_wasm.wasm
+flb-wamrc --size-level=3 --target=aarch64v8 --cpu=cortex-a57 -o /path/to/built_wasm.aot /path/to/built_wasm.wasm
 ```
 
 Then, when AOT (Ahead Of Time) compiling has succeeded:

development/wasm-input-plugins.md

@@ -25,9 +25,9 @@ Fluent Bit supports the following Wasm toolchains:
 Compile Fluent Bit with Wasm support. For example:
 
 ```text
-$ cd build/
-$ cmake ..
-$ make
+cd build/
+cmake ..
+make
 ```
 
 Once compiled, you can see new plugins that handle `wasm`. For example:
@@ -53,7 +53,7 @@ Wasm input in Fluent Bit assumes WASI ABI, also known as `wasm32-wasi` on Rust t
 TinyGo and WASI SDK support Wasm target by default. When using Rust's `wasm32-wasi` target, you must install `wasm32-wasi` by using [rustup](https://rustup.rs/). Then, install the target components as:
 
 ```text
-$ rustup target add wasm32-wasi
+rustup target add wasm32-wasi
 ```
 
 ### Requirements of Wasm/WASI programs

pipeline/inputs/cpu-metrics.md

@@ -40,7 +40,7 @@ In order to get the statistics of the CPU usage of your system, you can run the
 You can run this filter from the command line using a command like the following:
 
 ```shell
-$ build/bin/fluent-bit -i cpu -t my_cpu -o stdout -m '*'
+build/bin/fluent-bit -i cpu -t my_cpu -o stdout -m '*'
 ```
 
 The command returns results similar to the following:

pipeline/inputs/disk-io-metrics.md

@@ -24,7 +24,7 @@ In order to get disk usage from your system, you can run the plugin from the com
 You can run the plugin from the command line:
 
 ```shell
-$ fluent-bit -i disk -o stdout
+fluent-bit -i disk -o stdout
 ```
 
 Which returns information like the following:

pipeline/inputs/docker-events.md

@@ -21,7 +21,7 @@ This plugin supports the following configuration parameters:
 You can run this plugin from the command line:
 
 ```shell
-$ fluent-bit -i docker_events -o stdout
+fluent-bit -i docker_events -o stdout
 ```
 
 ### Configuration file

pipeline/inputs/dummy.md

@@ -29,7 +29,7 @@ You can run the plugin from the command line or through the configuration file:
 Run the plugin from the command line using the following command:
 
 ```shell
-$ fluent-bit -i dummy -o stdout
+fluent-bit -i dummy -o stdout
 ```
 
 which returns results like the following:

pipeline/inputs/ebpf.md

@@ -58,10 +58,10 @@ To enable the `in_ebpf` plugin, follow these steps to build Fluent Bit from sour
 
    ```bash
    # For YAML configuration.
-   $ sudo ./bin/fluent-bit --config fluent-bit.yaml
+   sudo ./bin/fluent-bit --config fluent-bit.yaml
 
    # For classic configuration.
-   $ sudo ./bin/fluent-bit --config fluent-bit.conf
+   sudo ./bin/fluent-bit --config fluent-bit.conf
    ```
 
 ## Configuration example

pipeline/inputs/elasticsearch.md

@@ -29,7 +29,7 @@ In order to start performing the checks, you can run the plugin from the command
 From the command line you can configure Fluent Bit to handle Bulk API requests with the following options:
 
 ```shell
-$ fluent-bit -i elasticsearch -p port=9200 -o stdout
+fluent-bit -i elasticsearch -p port=9200 -o stdout
 ```
 
 ### Configuration file