Apply suggestions from code review

Co-authored-by: Ryan Cartwright <[email protected]>

Author: davemooreuws

docs/guides/go/realtime-messaging.mdx

@@ -90,16 +90,6 @@ func main() {
   // Initialize a KV store named "connections" with Get, Set, and Delete permissions.
   connections := nitric.NewKv("connections").Allow(keyvalue.KvStoreGet, keyvalue.KvStoreSet, keyvalue.KvStoreDelete)
 
-  // Handle new WebSocket connections by storing the connection ID in the KV store.
-  ws.On(websockets.EventType_Connect, func(ctx *websockets.Ctx) {
-    err := connections.Set(context.TODO(), ctx.Request.ConnectionID(), map[string]interface{}{
-      "connectionId": ctx.Request.ConnectionID(),
-    })
-    if err != nil {
-      return
-    }
-  })
-
   // Add event handlers here
 
   nitric.Run()
@@ -108,8 +98,8 @@ func main() {
 
 Here we're creating:
 
-- A WebSocket endpoint named `public`
-- A Key-Value store named `connections` to track WebSocket connections
+- A [WebSocket](/websockets) endpoint named `public`
+- A [Key-Value store](/keyvalue) named `connections` to track WebSocket connections
 
 From here, let's add some features to that function that allow us to manage connections and broadcast messages.
 
@@ -150,6 +140,7 @@ ws.On(websockets.EventType_Message, func(ctx *websockets.Ctx) {
   if err != nil {
     return
   }
+  
   senderId := ctx.Request.ConnectionID()
 
   for {
@@ -205,15 +196,6 @@ func main() {
     }
   })
 
-  ws.On(websockets.EventType_Connect, func(ctx *websockets.Ctx) {
-    err := connections.Set(context.TODO(), ctx.Request.ConnectionID(), map[string]interface{}{
-      "connectionId": ctx.Request.ConnectionID(),
-    })
-    if err != nil {
-      return
-    }
-  })
-
   ws.On(websockets.EventType_Disconnect, func(ctx *websockets.Ctx) {
     err := connections.Delete(context.TODO(), ctx.Request.ConnectionID())
     if err != nil {
@@ -263,17 +245,13 @@ Now that you have your WebSocket application defined with handlers for each even
 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.
+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. If you want to update your services, just save them, and they'll be reloaded automatically.
+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. To do this, start by setting up your credentials and any configuration for the cloud you prefer:
-
-- [AWS](/reference/providers/aws)
-- [Azure](/reference/providers/azure)
-- [GCP](/reference/providers/gcp)
+At this point, you can deploy what you've built to any of the supported cloud providers. To do this, start by setting up your credentials and configuration for [AWS](/providers/pulumi/aws).
 
 Next, we'll need to create a `stack`. A stack represents a deployed instance of an application, which is a key value store of resources defined in your project. You might want separate stacks for each environment, such as stacks for `dev`, `test`, and `prod`. For now, let's start by creating a `dev` stack.
 

docs/guides/terraform/terratest.mdx

@@ -1,5 +1,5 @@
 ---
-description: Use Terratest to validate the infrastructure of a Nitric GO project deployed with Terraform
+description: Use Terratest to validate the infrastructure of a Nitric Go project deployed with Terraform
 tags:
   - Terraform
   - Testing
@@ -13,10 +13,10 @@ This guide will walk you through adding [Terratest](https://terratest.gruntwork.
 
 Terratest is designed to automate the entire process of testing your Terraform code with the following steps:
 
-- **Initialize**: Terratest will automatically run terraform init to initialize the Terraform working directory.
-- **Apply**: It will then run terraform apply to deploy the infrastructure as defined in your Terraform code.
+- **Initialize**: Terratest will automatically run `terraform init` to initialize the Terraform working directory.
+- **Apply**: It will then run `terraform apply` to deploy the infrastructure as defined in your Terraform code.
 - **Assert**: The test script will then run assertions to check that the infrastructure was created as expected.
-- **Teardown**: Finally, it will run terraform destroy to tear down the infrastructure after the test completes.
+- **Teardown**: Finally, it will run `terraform destroy` to tear down the infrastructure after the test completes.
 
 ## What we'll be doing
 
@@ -26,7 +26,7 @@ Terratest is designed to automate the entire process of testing your Terraform c
 
 ## Create and set up your application.
 
-Our sample project creates a real-time communication service using [websockets](/websockets) and a [key-value store](/keyvalue) for connections.
+Our sample project creates a real-time communication service using [WebSockets](/websockets) and a [key-value store](/keyvalue) for connections.
 
 We intend to deploy to AWS and will use Terratest to ensure that the following:
 
@@ -113,7 +113,7 @@ func main() {
 
 ## Deploying to AWS with a Terraform provider
 
-To deploy your application with Terraform you'll need to use Nitric's Terraform providers. You can learn more about using Nitric with Terraform [here](/reference/providers/terraform).
+To deploy your application with Terraform you'll need to use Nitric's Terraform providers. You can learn more about using Nitric with Terraform [here](/providers/terraform).
 
 ```
 nitric stack new dev aws-tf
@@ -156,7 +156,7 @@ go get github.com/aws/aws-sdk-go/aws/session
 go get github.com/aws/aws-sdk-go/service/apigatewayv2
 go get github.com/aws/aws-sdk-go/service/dynamodb
 go get github.com/aws/aws-sdk-go/service/iam
-```
+go get google.golang.org/genproto@latest
 
 ### Create the Test File
 
@@ -208,11 +208,11 @@ func TestTerraformResources(t *testing.T) {
 
 	// Test IAM role creation
 	iamClient := iam.New(sess)
-	roleName := "go-realtime_services-hello" // Name of the IAM role to check
+	roleName := "my-websocket-app_websockets-main" // Name of the IAM role to check
 	_, err = iamClient.GetRole(&iam.GetRoleInput{
 		RoleName: aws.String(roleName),
 	})
-	assert.NoError(t, err, "Expected IAM role 'go-realtime_services-hello' to be created")
+	assert.NoError(t, err, "Expected IAM role 'my-websocket-app_websockets-main' to be created")
 
 	// Test API gateway webSocket creation
 	apiClient := apigatewayv2.New(sess)