Simplify project so it doesn't need an update to the nitric.yaml config.

Author: raksiv

docs/guides/go/realtime-messaging.mdx

@@ -68,9 +68,9 @@ If everything is working as expected, you can now delete all files/folders in th
 
 ## Building the WebSocket Application
 
-Let's begin by setting up the WebSocket application. First, create a new folder called `websockets` within the services directory. Inside this folder, add a file named `main.go`, and include the following code:
+Let's begin by setting up the WebSocket application. Add a file named `main.go` to your 'services/' folder, and include the following code:
 
-```go title:services/websockets/main.go
+```go title:services/main.go
 package main
 
 import (
@@ -238,23 +238,14 @@ Do a quick `go mod tidy` to make sure all new dependencies are resolved.
 
 ## Ok, let's run this thing!
 
-Now that you have your WebSocket application defined with handlers for each event, it's time to test it locally. Update your `nitric.yaml` to point to the service at `websockets/main.go`:
-
-```yaml
-services:
-  - match: websockets/*
-    runtime: go
-    start: go run ./$SERVICE_PATH
-```
+Now that you have your WebSocket application defined with handlers for each event, it's time to test it locally.
 
 ```bash
 nitric start
 ```
 
 Once it starts, the application will be ready to accept WebSocket connections. You can use a WebSocket client like Postman or any other WebSocket tool to test the application. Alternatively, you can use the [Nitric Dashboard](/get-started/foundations/projects/local-development#local-dashboard).
 
-We will keep it running for our tests.
-
 ## Deploy to the cloud
 
 At this point, you can deploy what you've built to any of the supported cloud providers. In this example we'll deploy to AWS. Start by setting up your credentials and configuration for the [nitric/aws provider](/providers/pulumi/aws).