From 61257dc5b181b274cda1217c2baa58388f4ce685 Mon Sep 17 00:00:00 2001 From: owais-rehman Date: Tue, 18 Feb 2025 19:31:04 +0500 Subject: [PATCH] more lint correction --- .../how-to-guides/remote-debugging/remote-debugging-dotnet.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/for-developers/how-to-guides/remote-debugging/remote-debugging-dotnet.md b/content/for-developers/how-to-guides/remote-debugging/remote-debugging-dotnet.md index b33a2b33..f7753621 100644 --- a/content/for-developers/how-to-guides/remote-debugging/remote-debugging-dotnet.md +++ b/content/for-developers/how-to-guides/remote-debugging/remote-debugging-dotnet.md @@ -24,8 +24,8 @@ To enable remote debugging for your .NET application in a container, you need to Ensure that your Dockerfile is based on a .NET runtime or SDK image. You will typically have one of the following: -- SDK Image (for development and debugging): mcr.microsoft.com/dotnet/sdk: -- Runtime Image (for running the app): mcr.microsoft.com/dotnet/aspnet: +- `SDK Image` (for development and debugging): mcr.microsoft.com/dotnet/sdk: +- `Runtime Image` (for running the app): mcr.microsoft.com/dotnet/aspnet: If you're using a runtime-only image, debugging support might be limited, and you may need to switch to an SDK image for development.