Fixed pieces of formatting, spelling and typos in README.md (#72)

Author: nikelborm

.changeset/tender-queens-judge.md

@@ -0,0 +1,5 @@
+---
+"effect-vscode": patch
+---
+
+Fixed pieces of formatting, spelling, and typos in README.md

README.md

@@ -1,10 +1,10 @@
 # Effect Dev Tools
 
-View traces, metrics and inspect the context for your Effect app - all without leaving VSCode!
+View traces, metrics, and inspect the context for your Effect app - all without leaving VS Code!
 
 ## Setup
 
-To use Effect Dev Tools in your Effect project, first you need to install the following dependency:
+To use Effect Dev Tools in your Effect project, first, you need to install the following dependency:
 
 ```
 pnpm install @effect/experimental
@@ -27,20 +27,21 @@ const DevToolsLive = DevTools.layer()
 program.pipe(Effect.provide(DevToolsLive), NodeRuntime.runMain)
 ```
 
-The code above expects the DevTools server to be available at `localhost:34437`. If you are not running the DevTools client (e. g. backend) on the same machine, or if it's not available at localhost, you'll have to manully specify the websocket server url like so:
+The code above expects the `DevTools` server to be available at `localhost:34437`. If you are not running the `DevTools` client (e.g., backend) on the same machine, or if it's not available at `localhost`, you'll have to manually specify the websocket server URL like so:
+
 ```ts
 const DevToolsLive = DevTools.layer('ws://localhost:34437')
 ```
 
 If you are using `@effect/opentelemetry` in your project, then it is important that you provide the `DevTools` layer **before** your tracing layers, so the tracer is patched correctly.
 
-Beware, that Effect DevTools extension does not behave like typical debugger UI, which connects to debugger port of target process. It's the other way around here. One of the reasons for that is to enable tracing of web applications, which are not able to expose ports, as servers do.
+Beware that the Effect DevTools extension does not behave like a typical debugger UI, which connects to the debugger port of the target process. It's the other way around here. One of the reasons for that is to enable tracing of web applications, which are not able to expose ports, as servers do.
 
 ### Docker
 
-In case you're using docker for local development and want to connect from your containerized application to DevTools server in VS Code, you'll have to do 2 things.
+In case you're using Docker for local development and want to connect from your containerized application to the DevTools server in VS Code, you'll have to do 2 things.
 
-1. You'll have to make your host machine addressable from within the container, by adding extra host.
+1. You'll have to make your host machine addressable from within the container by adding an extra host.
 
 ```yaml
 services:
@@ -49,14 +50,14 @@ services:
       - host.docker.internal:host-gateway
 ```
 
-2. You'll have to specify connection URL in your application to be
+2. You'll have to specify the connection URL in your application to be
 
 ```ts
 DevTools.layer('ws://host.docker.internal:34437');
 ```
 
 ## Usage
 
-Once you have added the Layer to your project, open the Effect Dev Tools panel in vscode & click "Start the server" in the "Clients" panel.
+Once you have added the Layer to your project, open the Effect Dev Tools panel in VS Code & click "Start the server" in the "Clients" panel.
 
 You can then start your Effect app, and then begin to inspect the results!