Fix format

Author: chalin

content/en/docs/languages/dotnet/getting-started.md

@@ -264,7 +264,8 @@ Value: Sum: 1330.4766000000002 Count: 5 Min: 50.0333 Max: 465.7936
 For more:
 
 - Run this example with another [exporter][] for telemetry data.
-- Try [automatic instrumentation](/docs/zero-code/dotnet/) on one of your own apps.
+- Try [automatic instrumentation](/docs/zero-code/dotnet/) on one of your own
+  apps.
 - Learn about [manual instrumentation][] and try out more
   [examples](/docs/languages/dotnet/examples/).
 - Take a look at the [OpenTelemetry Demo](/docs/demo/), which includes .NET

content/en/docs/languages/dotnet/instrumentation.md

@@ -39,8 +39,8 @@ you can refer to the [OpenTelemetry API Shim docs for tracing](../shim).
 ## Example app preparation {#example-app}
 
 This page uses a modified version of the example app from
-[Getting Started](/docs/languages/dotnet/getting-started/) to help you learn about
-manual instrumentation.
+[Getting Started](/docs/languages/dotnet/getting-started/) to help you learn
+about manual instrumentation.
 
 You don't have to use the example app: if you want to instrument your own app or
 library, follow the instructions here to adapt the process to your own code.
@@ -307,8 +307,8 @@ loggerFactory.Dispose();
 For debugging and local development purposes, the example exports telemetry to
 the console. After you have finished setting up manual instrumentation, you need
 to configure an appropriate exporter to
-[export the app's telemetry data](/docs/languages/dotnet/exporters/) to one or more
-telemetry backends.
+[export the app's telemetry data](/docs/languages/dotnet/exporters/) to one or
+more telemetry backends.
 
 The example also sets up the mandatory SDK default attribute `service.name`,
 which holds the logical name of the service, and the optional, but highly
@@ -689,5 +689,5 @@ You'll also want to configure an appropriate exporter to
 [export your telemetry data](../exporters/) to one or more telemetry backends.
 
 You can also check the
-[automatic instrumentation for .NET](/docs/zero-code/dotnet/), which is currently
-in beta.
+[automatic instrumentation for .NET](/docs/zero-code/dotnet/), which is
+currently in beta.

content/en/docs/languages/dotnet/libraries.md

@@ -116,8 +116,8 @@ You can also find more instrumentations available in the
 ## Next steps
 
 After you have set up instrumentation libraries, you may want to add your own
-[instrumentation](/docs/languages/dotnet/instrumentation) to your code, to collect
-custom telemetry data.
+[instrumentation](/docs/languages/dotnet/instrumentation) to your code, to
+collect custom telemetry data.
 
 If you are using .NET Framework 4.x instead of modern .NET, refer to the
 [.NET Framework docs](/docs/languages/dotnet/netframework) to configure
@@ -128,7 +128,7 @@ You'll also want to configure an appropriate exporter to
 telemetry backends.
 
 You can also check the
-[automatic instrumentation for .NET](/docs/zero-code/dotnet), which is currently in
-beta.
+[automatic instrumentation for .NET](/docs/zero-code/dotnet), which is currently
+in beta.
 
 [opentelemetry-dotnet]: https://github.com/open-telemetry/opentelemetry-dotnet

content/en/docs/languages/dotnet/netframework.md

@@ -146,13 +146,13 @@ exception on the `Activity` itself as an `ActivityEvent`.
 
 After you have observability generated automatically with instrumentation
 libraries, you may want to add
-[manual instrumentation](/docs/languages/dotnet/instrumentation) to collect custom
-telemetry data.
+[manual instrumentation](/docs/languages/dotnet/instrumentation) to collect
+custom telemetry data.
 
 You'll also want to configure an appropriate exporter to
 [export your telemetry data](/docs/languages/dotnet/exporters) to one or more
 telemetry backends.
 
 You can also check the
-[automatic instrumentation for .NET](/docs/zero-code/dotnet), which is currently in
-beta.
+[automatic instrumentation for .NET](/docs/zero-code/dotnet), which is currently
+in beta.

content/en/docs/zero-code/dotnet/_index.md

@@ -296,5 +296,5 @@ For general troubleshooting steps and solutions to specific issues, see
 
 After you have automatic instrumentation configured for your app or service, you
 might want to [send custom traces and metrics](./custom) or add
-[manual instrumentation](/docs/languages/dotnet/instrumentation) to collect custom
-telemetry data.
+[manual instrumentation](/docs/languages/dotnet/instrumentation) to collect
+custom telemetry data.