Fixed links to dotnet and go

Author: Evanthx

docs/develop/dotnet/nexus/feature-guide.mdx

@@ -195,7 +195,7 @@ public IOperationHandler<INexusGreetingService.GetLanguagesInput, INexusGreeting
     ...
 ```
 
-There are two examples of messaging through Nexus in the sample code: the [caller pattern](https://github.com/temporalio/samples-dotnet/tree/src/NexusMessaging/CallerPattern/) and the [on-demand pattern](https://github.com/temporalio/samples-dotnet/tree/src/NexusMessaging/OnDemandPattern/).
+There are two examples of messaging through Nexus in the sample code: the [caller pattern](https://github.com/temporalio/samples-dotnet/tree/main/src/NexusMessaging/CallerPattern) and the [on-demand pattern](https://github.com/temporalio/samples-dotnet/tree/main/src/NexusMessaging/OnDemandPattern).
 The caller pattern shows how to send messages to an existing Workflow, while the on-demand pattern shows how to start a Workflow through Nexus and then send Signals to it.
 
 ### Develop an Asynchronous Nexus Operation handler to start a Workflow

docs/develop/go/nexus/feature-guide.mdx

@@ -179,7 +179,7 @@ The [nexus_messaging](https://github.com/temporalio/samples-go/tree/main/nexus-m
 Use the Nexus library, as shown below, to get the Client that the Worker was initialized with. In this example, the Workflow Id is derived from the client Id, with the `GetWorkflowID` method. This converts a given client Id (in this case, the client is passing in a user Id) to generate a Workflow Id from it.
 This way the client only needs the identifier it cares about.
 
-[nexus-messaging/callerpattern/handler/app.go](https://github.com/temporalio/samples-go/blob/nexus-messaging/callerpattern/handler/app.go)
+[nexus-messaging/callerpattern/handler/app.go](https://github.com/temporalio/samples-go/blob/main/nexus-messaging/callerpattern/handler/app.go)
 
 ```go
 func GetWorkflowID(userID string) string {