Resolve merge conflicts in README files

components/backends/trtllm/README.md

@@ -222,17 +222,9 @@ The migrated request will continue responding to the original request, allowing
 
 See [client](../llm/README.md#client) section to learn how to send request to the deployment.
 
-<<<<<<< HEAD
-NOTE: To send a request to a multi-node deployment, target the node which is running `dynamo-run in=http`.
-=======
 NOTE: To send a request to a multi-node deployment, target the node which is running `python3 -m dynamo.frontend <args>`.
->>>>>>> origin/main
 
 ## Benchmarking
 
 To benchmark your deployment with GenAI-Perf, see this utility script, configuring the
-<<<<<<< HEAD
-`model` name and `host` based on your deployment: [perf.sh](../../benchmarks/llm/perf.sh)
-=======
 `model` name and `host` based on your deployment: [perf.sh](../../../benchmarks/llm/perf.sh)
->>>>>>> origin/main

components/backends/vllm/README.md

@@ -81,11 +81,7 @@ This includes the specific commit [vllm-project/vllm#19790](https://github.com/v
 ## Run Single Node Examples
 
 > [!IMPORTANT]
-<<<<<<< HEAD
-> Below we provide simple shell scripts that run the components for each configuration. Each shell script runs `python3 dynamo.frontend` to start the ingress and uses `python3 dynamo.vllm` to start the vLLM workers. You can also run each command in separate terminals for better log visibility.
-=======
 > Below we provide simple shell scripts that run the components for each configuration. Each shell script runs `python3 -m dynamo.frontend` to start the ingress and uses `python3 -m dynamo.vllm` to start the vLLM workers. You can also run each command in separate terminals for better log visibility.
->>>>>>> origin/main
 
 This figure shows an overview of the major components to deploy: