Skip to content

Commit d1ef521

Browse files
chalinchalin
authored
[IA] Rename net to dotnet in /docs/{languages,zero-code}/net, add redirects and adjust links (#6590)
1 parent adf1731 commit d1ef521

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

45 files changed

+75
-70
lines changed

‎.htmltest.yml

+1-1
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ IgnoreURLs: # list of regexs of paths or URLs to be ignored
2828
- ^/api/?$
2929
- ^((/..)?/docs/languages/\w+|\.\.)/(api|examples|registry)/$
3030
- ^(/..)?/docs/collector/registry/$
31-
- ^(/..)?/docs/languages/net/(metrics-api|traces-api)/
31+
- ^(/..)?/docs/languages/dotnet/(metrics-api|traces-api)/
3232
- ^((/..)?/docs/migration/)?opencensus/$
3333
- ^(/community/end-user/)?feedback-survey/$
3434
- ^/../docs/specs/?$ # non-default locale spec redirect

‎content/en/blog/2022/frontend-overhaul/index.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ The demo’s stack includes multiple microservices in different languages,
5555
covering each of the following OTel-supported languages:
5656

5757
- [C++](/docs/languages/cpp/)
58-
- [.NET](/docs/languages/net/)
58+
- [.NET](/docs/languages/dotnet/)
5959
- [Erlang/Elixir](/docs/languages/erlang/)
6060
- [Go](/docs/languages/go/)
6161
- [Node.js](/docs/languages/js/)

‎content/en/blog/2023/end-user-discussions-03.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -190,7 +190,7 @@ agent to the host metrics receiver for infrastructure monitoring.
190190
maturing in OTel; for example, the Java JAR agent takes care of instrumenting
191191
[most libraries](https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/docs/supported-libraries.md#libraries--frameworks)
192192
that are used by applications. Auto-instrumentation is also available for
193-
[Python](/docs/zero-code/python/), [.NET](/docs/zero-code/net/), and
193+
[Python](/docs/zero-code/python/), [.NET](/docs/zero-code/dotnet/), and
194194
[Node.js](/docs/zero-code/js/).
195195
- If you’re using Kubernetes, they can use the
196196
[OTel operator](https://github.com/open-telemetry/opentelemetry-operator),

‎content/en/blog/2023/otel-dotnet-auto-instrumentation.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ package that simplify the task of deploying and configuring the collection of
2020
telemetry. The automatic instrumentation is fully compatible with manual
2121
instrumentation in case you need to send custom spans or metrics.
2222

23-
To get started, [read the documentation](/docs/zero-code/net) or browse the
23+
To get started, [read the documentation](/docs/zero-code/dotnet) or browse the
2424
[examples](https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/tree/main/examples)
2525
for demonstrations of different instrumentation scenarios covered by the
2626
OpenTelemetry .NET Automatic Instrumentation.

‎content/en/blog/2023/otel-in-focus-02.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ planning a release of new documentation for PHP soon.
7676
has been released with deprecations to Jaeger exporters, several performance
7777
improvements and bugfixes, and changes to Prometheus export.
7878

79-
##### [.NET](/docs/languages/net/)
79+
##### [.NET](/docs/languages/dotnet/)
8080

8181
[v1.4](https://github.com/open-telemetry/opentelemetry-dotnet/releases/tag/core-1.4.0)
8282
removes several deprecated extension methods.

‎content/en/blog/2023/otel-in-focus-05.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,7 @@ exporting, and suppressing instrumentation.
8686
`opentelemetry.sdk.metrics.view`
8787
- Fix headers types mismatch for OTLP Exporters
8888

89-
#### [.NET](/docs/languages/net/)
89+
#### [.NET](/docs/languages/dotnet/)
9090

9191
[Version 1.5.0-rc1](https://github.com/open-telemetry/opentelemetry-dotnet/releases/tag/core-1.5.0-rc.1)
9292
includes many bugfixes across a variety of packages.

‎content/en/blog/2023/otel-in-focus-06.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -113,7 +113,7 @@ has been released, requiring some migrations to be performed.
113113
[Version 1.14](https://github.com/open-telemetry/opentelemetry-js/releases/tag/v1.14.0)
114114
includes an optional `forceFlush` method to the `SpanExporter` interface.
115115

116-
#### [.NET](/docs/languages/net/)
116+
#### [.NET](/docs/languages/dotnet/)
117117

118118
[Version 1.5.1](https://github.com/open-telemetry/opentelemetry-dotnet/releases/tag/core-1.5.1)
119119
has been released, as well as 1.5.0. 1.5.1 is a fix for issues introduced in

‎content/en/blog/2023/otel-in-focus-07.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ includes updates to OTLP and log support.
7272
includes metric bug fixes for histograms and exponential histograms. In
7373
addition, OTLP support has been updated.
7474

75-
#### [.NET](/docs/languages/net/)
75+
#### [.NET](/docs/languages/dotnet/)
7676

7777
[Version 1.6.0-alpha.1](https://github.com/open-telemetry/opentelemetry-dotnet/releases/tag/core-1.6.0-alpha.1)
7878
has been released. 1.6 re-introduces support for exemplars, as well as

‎content/en/blog/2023/otel-in-focus-08.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -89,7 +89,7 @@ the OTLP exporter.
8989
[Version 1.15.2](https://github.com/open-telemetry/opentelemetry-js/releases/tag/v1.15.1)
9090
fixes several bugs.
9191

92-
#### [.NET](/docs/languages/net/)
92+
#### [.NET](/docs/languages/dotnet/)
9393

9494
[Version 1.6.0-rc.1](https://github.com/open-telemetry/opentelemetry-dotnet/releases/tag/core-1.6.0-rc.1)
9595
has been released, bringing small changes to metrics, export, and an

‎content/en/blog/2023/otel-in-focus-09.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -188,7 +188,7 @@ fixes an unintentional breaking change in previous releases.
188188
There have been several important changes in the experimental packages,
189189
including deprecation of legacy configuration APIs.
190190

191-
#### [.NET](/docs/languages/net/)
191+
#### [.NET](/docs/languages/dotnet/)
192192

193193
[Version 1.6.0](https://github.com/open-telemetry/opentelemetry-dotnet/releases/tag/core-1.6.0)
194194
includes minor updates to metrics.

‎content/en/blog/2023/otel-in-focus-10.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -119,7 +119,7 @@ fixes several bugs in tracing and metrics. Experimental builds include several
119119
bug fixes and enhancements to the logging exporter, the deprecation of direct
120120
Jaeger export, and more.
121121

122-
#### [.NET](/docs/languages/net/)
122+
#### [.NET](/docs/languages/dotnet/)
123123

124124
[Version 1.7.0-alpha](https://github.com/open-telemetry/opentelemetry-dotnet/releases/tag/core-1.7.0-alpha.1)
125125
includes many bug fixes and updates, including some breaking changes.

‎content/en/docs/concepts/instrumentation/zero-code/index.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ Other configuration options are available, including:
4646

4747
Automatic instrumentation is available for the following languages:
4848

49-
- [.NET](/docs/zero-code/net/)
49+
- [.NET](/docs/zero-code/dotnet/)
5050
- [Go](/docs/zero-code/go)
5151
- [Java](/docs/zero-code/java/)
5252
- [JavaScript](/docs/zero-code/js/)

‎content/en/docs/getting-started/dev.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ Next, you can deep dive into the documentations for the
2626
[language](../../languages/) you are using:
2727

2828
- [C++](../../languages/cpp/)
29-
- [.NET](../../languages/net/)
29+
- [.NET](../../languages/dotnet/)
3030
- [Erlang / Elixir](../../languages/erlang/)
3131
- [Go](../../languages/go/)
3232
- [Java](../../languages/java/)

‎content/en/docs/languages/_index.md

+3-1
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,9 @@ description:
55
languages
66
weight: 250
77
aliases: [/docs/instrumentation]
8-
redirects: [{ from: /docs/instrumentation/*, to: ':splat' }] # Only for `en`
8+
redirects:
9+
- { from: /docs/instrumentation/*, to: ':splat' } # Only for `en`
10+
- { from: 'net/*', to: 'dotnet/:splat' }
911
---
1012

1113
OpenTelemetry code [instrumentation][] is supported for the languages listed in

‎content/en/docs/languages/net/_index.md ‎content/en/docs/languages/dotnet/_index.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: .NET
33
description: >
44
<img width="35" class="img-initial" src="/img/logos/32x32/dotnet.svg"
55
alt=".NET"> A language-specific implementation of OpenTelemetry in .NET.
6-
aliases: [/csharp, /csharp/metrics, /csharp/tracing]
6+
aliases: [net, /csharp, /csharp/metrics, /csharp/tracing]
77
weight: 12
88
---
99

‎content/en/docs/languages/net/examples.md ‎content/en/docs/languages/dotnet/examples.md

File renamed without changes.

‎content/en/docs/languages/net/exporters.md ‎content/en/docs/languages/dotnet/exporters.md

File renamed without changes.

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

+5-4
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ cSpell:ignore: ASPNETCORE rolldice
88
This page will show you how to get started with OpenTelemetry in .NET.
99

1010
If you are looking for a way to automatically instrument your application, check
11-
out [this guide](/docs/zero-code/net/getting-started/).
11+
out [this guide](/docs/zero-code/dotnet/getting-started/).
1212

1313
You will learn how you can instrument a simple .NET application, in such a way
1414
that [traces][], [metrics][] and [logs][] are emitted to the console.
@@ -28,7 +28,7 @@ you can use OpenTelemetry .NET with other frameworks as well. For a complete
2828
list of libraries for supported frameworks, see the
2929
[registry](/ecosystem/registry/?component=instrumentation&language=dotnet).
3030

31-
For more elaborate examples, see [examples](/docs/languages/net/examples/).
31+
For more elaborate examples, see [examples](/docs/languages/dotnet/examples/).
3232

3333
### Create and launch an HTTP Server
3434

@@ -264,9 +264,10 @@ Value: Sum: 1330.4766000000002 Count: 5 Min: 50.0333 Max: 465.7936
264264
For more:
265265

266266
- Run this example with another [exporter][] for telemetry data.
267-
- Try [automatic instrumentation](/docs/zero-code/net/) on one of your own apps.
267+
- Try [automatic instrumentation](/docs/zero-code/dotnet/) on one of your own
268+
apps.
268269
- Learn about [manual instrumentation][] and try out more
269-
[examples](/docs/languages/net/examples/).
270+
[examples](/docs/languages/dotnet/examples/).
270271
- Take a look at the [OpenTelemetry Demo](/docs/demo/), which includes .NET
271272
based [Cart Service](/docs/demo/services/cart/).
272273

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

+11-11
Original file line numberDiff line numberDiff line change
@@ -12,12 +12,12 @@ cSpell:ignore: dicelib rolldice
1212

1313
On this page you will learn how you can add traces, metrics and logs to your
1414
code manually. You are not limited to using one kind of instrumentation: you can
15-
also use [automatic instrumentation](/docs/zero-code/net/) to get started and
15+
also use [automatic instrumentation](/docs/zero-code/dotnet/) to get started and
1616
then enrich your code with manual instrumentation as needed.
1717

1818
Also, for libraries your code depends on, you don't have to write
1919
instrumentation code yourself, since they might be already instrumented or there
20-
are [instrumentation libraries](/docs/languages/net/libraries/) for them.
20+
are [instrumentation libraries](/docs/languages/dotnet/libraries/) for them.
2121

2222
{{% /alert %}}
2323

@@ -39,8 +39,8 @@ you can refer to the [OpenTelemetry API Shim docs for tracing](../shim).
3939
## Example app preparation {#example-app}
4040

4141
This page uses a modified version of the example app from
42-
[Getting Started](/docs/languages/net/getting-started/) to help you learn about
43-
manual instrumentation.
42+
[Getting Started](/docs/languages/dotnet/getting-started/) to help you learn
43+
about manual instrumentation.
4444

4545
You don't have to use the example app: if you want to instrument your own app or
4646
library, follow the instructions here to adapt the process to your own code.
@@ -307,15 +307,15 @@ loggerFactory.Dispose();
307307
For debugging and local development purposes, the example exports telemetry to
308308
the console. After you have finished setting up manual instrumentation, you need
309309
to configure an appropriate exporter to
310-
[export the app's telemetry data](/docs/languages/net/exporters/) to one or more
311-
telemetry backends.
310+
[export the app's telemetry data](/docs/languages/dotnet/exporters/) to one or
311+
more telemetry backends.
312312

313313
The example also sets up the mandatory SDK default attribute `service.name`,
314314
which holds the logical name of the service, and the optional, but highly
315315
encouraged, attribute `service.version`, which holds the version of the service
316316
API or implementation. Alternative methods exist for setting up resource
317317
attributes. For more information, see
318-
[Resources](/docs/languages/net/resources/).
318+
[Resources](/docs/languages/dotnet/resources/).
319319

320320
To verify your code, build and run the app:
321321

@@ -670,13 +670,13 @@ private int rollOnce()
670670

671671
The documentation for the metrics API & SDK is missing, you can help make it
672672
available by
673-
[editing this page](https://github.com/open-telemetry/opentelemetry.io/edit/main/content/en/docs/languages/net/instrumentation.md).
673+
[editing this page](https://github.com/open-telemetry/opentelemetry.io/edit/main/content/en/docs/languages/dotnet/instrumentation.md).
674674

675675
## Logs
676676

677677
The documentation for the logs API and SDK is missing. You can help make it
678678
available by
679-
[editing this page](https://github.com/open-telemetry/opentelemetry.io/edit/main/content/en/docs/languages/net/instrumentation.md).
679+
[editing this page](https://github.com/open-telemetry/opentelemetry.io/edit/main/content/en/docs/languages/dotnet/instrumentation.md).
680680

681681
## Next steps
682682

@@ -689,5 +689,5 @@ You'll also want to configure an appropriate exporter to
689689
[export your telemetry data](../exporters/) to one or more telemetry backends.
690690

691691
You can also check the
692-
[automatic instrumentation for .NET](/docs/zero-code/net/), which is currently
693-
in beta.
692+
[automatic instrumentation for .NET](/docs/zero-code/dotnet/), which is
693+
currently in beta.

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

+6-6
Original file line numberDiff line numberDiff line change
@@ -116,19 +116,19 @@ You can also find more instrumentations available in the
116116
## Next steps
117117

118118
After you have set up instrumentation libraries, you may want to add your own
119-
[instrumentation](/docs/languages/net/instrumentation) to your code, to collect
120-
custom telemetry data.
119+
[instrumentation](/docs/languages/dotnet/instrumentation) to your code, to
120+
collect custom telemetry data.
121121

122122
If you are using .NET Framework 4.x instead of modern .NET, refer to the
123-
[.NET Framework docs](/docs/languages/net/netframework) to configure
123+
[.NET Framework docs](/docs/languages/dotnet/netframework) to configure
124124
OpenTelemetry and instrumentation libraries on .NET Framework.
125125

126126
You'll also want to configure an appropriate exporter to
127-
[export your telemetry data](/docs/languages/net/exporters) to one or more
127+
[export your telemetry data](/docs/languages/dotnet/exporters) to one or more
128128
telemetry backends.
129129

130130
You can also check the
131-
[automatic instrumentation for .NET](/docs/zero-code/net), which is currently in
132-
beta.
131+
[automatic instrumentation for .NET](/docs/zero-code/dotnet), which is currently
132+
in beta.
133133

134134
[opentelemetry-dotnet]: https://github.com/open-telemetry/opentelemetry-dotnet

‎content/en/docs/languages/net/metrics-api.md ‎content/en/docs/languages/dotnet/metrics-api.md

File renamed without changes.

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

+5-5
Original file line numberDiff line numberDiff line change
@@ -146,13 +146,13 @@ exception on the `Activity` itself as an `ActivityEvent`.
146146

147147
After you have observability generated automatically with instrumentation
148148
libraries, you may want to add
149-
[manual instrumentation](/docs/languages/net/instrumentation) to collect custom
150-
telemetry data.
149+
[manual instrumentation](/docs/languages/dotnet/instrumentation) to collect
150+
custom telemetry data.
151151

152152
You'll also want to configure an appropriate exporter to
153-
[export your telemetry data](/docs/languages/net/exporters) to one or more
153+
[export your telemetry data](/docs/languages/dotnet/exporters) to one or more
154154
telemetry backends.
155155

156156
You can also check the
157-
[automatic instrumentation for .NET](/docs/zero-code/net), which is currently in
158-
beta.
157+
[automatic instrumentation for .NET](/docs/zero-code/dotnet), which is currently
158+
in beta.

‎content/en/docs/languages/net/registry.md ‎content/en/docs/languages/dotnet/registry.md

File renamed without changes.

‎content/en/docs/languages/net/resources.md ‎content/en/docs/languages/dotnet/resources.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -137,7 +137,7 @@ code, the values in code take precedence.
137137
There are more resource detectors you can add to your configuration, for example
138138
to get details about your [Cloud] environment or [Deployment][].
139139

140-
[getting started]: /docs/languages/net/getting-started/
140+
[getting started]: /docs/languages/dotnet/getting-started/
141141
[host]: /docs/specs/semconv/resource/host/
142142
[cloud]: /docs/specs/semconv/resource/cloud/
143143
[deployment]: /docs/specs/semconv/resource/deployment-environment/

‎content/en/docs/languages/net/shim.md ‎content/en/docs/languages/dotnet/shim.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -413,10 +413,10 @@ This will capture things like the current stack trace as attributes in the span.
413413
## Next steps
414414

415415
After you've setup manual instrumentation, you may want to use
416-
[instrumentation libraries](/docs/languages/net/libraries). Instrumentation
416+
[instrumentation libraries](/docs/languages/dotnet/libraries). Instrumentation
417417
libraries will instrument relevant libraries you're using and generate data for
418418
things like inbound and outbound HTTP requests and more.
419419

420420
You'll also want to configure an appropriate exporter to
421-
[export your telemetry data](/docs/languages/net/exporters) to one or more
421+
[export your telemetry data](/docs/languages/dotnet/exporters) to one or more
422422
telemetry backends.

‎content/en/docs/languages/net/traces-api.md ‎content/en/docs/languages/dotnet/traces-api.md

File renamed without changes.

‎content/en/docs/migration/opentracing.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -181,7 +181,7 @@ For details on how each OpenTracing shim works, see the appropriate
181181
language-specific documentation. For details on the design of the OpenTracing
182182
shim, see [OpenTracing Compatibility][ot_spec].
183183

184-
[.net]: /docs/languages/net/shim/
184+
[.net]: /docs/languages/dotnet/shim/
185185
[go]: https://pkg.go.dev/go.opentelemetry.io/otel/bridge/opentracing
186186
[java]:
187187
https://github.com/open-telemetry/opentelemetry-java/tree/main/opentracing-shim

‎content/en/docs/platforms/kubernetes/operator/automatic.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -178,7 +178,7 @@ spec:
178178
179179
#### Learn more {#dotnet-learn-more}
180180
181-
For more details, see [.NET Auto Instrumentation docs](/docs/zero-code/net/).
181+
For more details, see [.NET Auto Instrumentation docs](/docs/zero-code/dotnet/).
182182
183183
### Deno
184184

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

+1
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
22
title: Zero-code Instrumentation
3+
redirects: [{ from: 'net/*', to: 'dotnet/:splat' }]
34
weight: 260
45
---
56

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

+5-4
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,9 @@
22
title: .NET zero-code instrumentation
33
description: Send traces and metrics from .NET applications and services.
44
linkTitle: .NET
5-
weight: 30
5+
aliases: [net]
66
redirects: [{ from: /docs/languages/net/automatic/*, to: ':splat' }]
7+
weight: 30
78
cSpell:ignore: coreutils HKLM iisreset myapp
89
---
910

@@ -12,7 +13,7 @@ from .NET applications and services to observability backends without having to
1213
modify their source code.
1314

1415
To learn how to instrument your service or application code, read
15-
[Manual instrumentation](/docs/languages/net/instrumentation).
16+
[Manual instrumentation](/docs/languages/dotnet/instrumentation).
1617

1718
## Compatibility
1819

@@ -295,5 +296,5 @@ For general troubleshooting steps and solutions to specific issues, see
295296

296297
After you have automatic instrumentation configured for your app or service, you
297298
might want to [send custom traces and metrics](./custom) or add
298-
[manual instrumentation](/docs/languages/net/instrumentation) to collect custom
299-
telemetry data.
299+
[manual instrumentation](/docs/languages/dotnet/instrumentation) to collect
300+
custom telemetry data.

‎content/en/docs/zero-code/net/configuration.md ‎content/en/docs/zero-code/dotnet/configuration.md

File renamed without changes.

‎content/en/docs/zero-code/net/custom.md ‎content/en/docs/zero-code/dotnet/custom.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -87,4 +87,4 @@ To create your custom metrics manually, follow these steps:
8787

8888
## Further reading
8989

90-
- [OpenTelemetry.io documentation for .NET Manual Instrumentation](/docs/languages/net/instrumentation#setting-up-an-activitysource)
90+
- [OpenTelemetry.io documentation for .NET Manual Instrumentation](/docs/languages/dotnet/instrumentation#setting-up-an-activitysource)

‎content/en/docs/zero-code/net/getting-started.md ‎content/en/docs/zero-code/dotnet/getting-started.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ This page will show you how to get started with OpenTelemetry .NET Automatic
99
Instrumentation.
1010

1111
If you are looking for a way to manually instrument your application, check out
12-
[this guide](/docs/languages/net/getting-started).
12+
[this guide](/docs/languages/dotnet/getting-started).
1313

1414
You will learn how you can instrument a simple .NET application automatically,
1515
in such a way that [traces][], [metrics][] and [logs][] are emitted to the
@@ -28,7 +28,7 @@ The following example uses a basic
2828
application. If you are not using ASP.NET Core, that's OK — you can still use
2929
OpenTelemetry .NET Automatic Instrumentation.
3030

31-
For more elaborate examples, see [examples](/docs/languages/net/examples/).
31+
For more elaborate examples, see [examples](/docs/languages/dotnet/examples/).
3232

3333
### Create and launch an HTTP Server
3434

‎content/en/docs/zero-code/net/instrumentations.md ‎content/en/docs/zero-code/dotnet/instrumentations.md

File renamed without changes.

‎content/en/docs/zero-code/net/nuget-packages.md ‎content/en/docs/zero-code/dotnet/nuget-packages.md

File renamed without changes.

‎content/en/docs/zero-code/net/troubleshooting.md ‎content/en/docs/zero-code/dotnet/troubleshooting.md

File renamed without changes.

‎content/es/docs/getting-started/dev.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ Luego, puedes profundizar en la documentación por
2828
[lenguaje de programación](../../languages/) que estás utilizando:
2929

3030
- [C++](../../languages/cpp/)
31-
- [.NET](../../languages/net/)
31+
- [.NET](../../languages/dotnet/)
3232
- [Erlang / Elixir](../../languages/erlang/)
3333
- [Go](../../languages/go/)
3434
- [Java](../../languages/java/)

‎content/ja/docs/concepts/instrumentation/zero-code/index.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ OpenTelemetry を使えば、[コードベースの計装](/docs/concepts/instru
3333

3434
ゼロコード計装は以下の言語に対応しています。
3535

36-
- [.NET](/docs/zero-code/net/)
36+
- [.NET](/docs/zero-code/dotnet/)
3737
- [Go](/docs/zero-code/go)
3838
- [Java](/docs/zero-code/java/)
3939
- [JavaScript](/docs/zero-code/js/)

0 commit comments

Comments
 (0)