diff --git a/packages/http-server-csharp/docs/usage.md b/packages/http-server-csharp/docs/usage.md
index d6291d2ad8c..e1d2436b2ee 100644
--- a/packages/http-server-csharp/docs/usage.md
+++ b/packages/http-server-csharp/docs/usage.md
@@ -79,7 +79,7 @@ Models are partial, so you can add additional members for internal usage as need
 
 After successful generation, you should:
 
-- Use the SwaggerUI endpoint to test out the running service
+- Use the SwaggerUI endpoint (`/swagger`) to test out the running service
 - Implement the business logic interfaces for your operations
 - Update MockRegistration.cs, or register each of your interfaces as part of application startup
 - Update configuration to suit your needs
diff --git a/packages/http-server-csharp/src/lib/doc.ts b/packages/http-server-csharp/src/lib/doc.ts
index e6b22df1653..6359a0d93cb 100644
--- a/packages/http-server-csharp/src/lib/doc.ts
+++ b/packages/http-server-csharp/src/lib/doc.ts
@@ -40,7 +40,7 @@ title: Next Steps
 
 # Next Steps
 
-- Use the SwaggerUI endpoint to test out the running service
+- Use the SwaggerUI endpoint (`/swagger`) to test out the running service
 - Implement business logic interfaces for your operations
 - Register each of your implementations as part of application startup
 - Update development and production configuration to suit your needs
@@ -134,7 +134,7 @@ Models are partial, so you can add additional members for internal usage as need
 
 After successful generation, you should:
 
-- Use the SwaggerUI endpoint to test out the running service
+- Use the SwaggerUI endpoint (`/swagger`)  to test out the running service
 - Implement the business logic interfaces for your operations
 - Update MockRegistration.cs, or register each of your interfaces as part of application startup
 - Update configuration to suit your needs
@@ -235,7 +235,7 @@ title: Next Steps
 
 # Next Steps
 
-- Use the SwaggerUI endpoint to test out the running service
+- Use the SwaggerUI endpoint (`/swagger`) to test out the running service
 - Update business logic mocks with real business logic
 ${mocks.flatMap((m) => `  - \`mocks/${m.className}.cs\``).join("\n")}
 - Update \`mocks/MockRegistration.cs\` if you update the constructor of business logic implementations.
diff --git a/website/src/content/docs/docs/emitters/servers/http-server-csharp/project.md b/website/src/content/docs/docs/emitters/servers/http-server-csharp/project.md
index e10eee91a7c..a3d5f419096 100644
--- a/website/src/content/docs/docs/emitters/servers/http-server-csharp/project.md
+++ b/website/src/content/docs/docs/emitters/servers/http-server-csharp/project.md
@@ -92,7 +92,7 @@ Models are partial, so you can add additional members for internal usage as need
 
 After successful generation, you should:
 
-- Use the SwaggerUI endpoint to test out the running service
+- Use the SwaggerUI endpoint (`/swagger`) to test out the running service
 - Implement the business logic interfaces for your operations
 - Update MockRegistration.cs, or register each of your interfaces as part of application startup
 - Update configuration to suit your needs