Move to .NET install page.

content/en/serverless/aws_lambda/configuration.md

@@ -345,15 +345,6 @@ For a more granular approach, use these service-specific identifiers:
 
 For renaming downstream services, see `DD_SERVICE_MAPPING` in the [tracer's config documentation][45].
 
-## Install Datadog tracer for .NET
-
-Special care must be taken when installing the Datadog tracer when also using the [Datadog Lambda tracing layer for .NET](https://github.com/DataDog/dd-trace-dotnet-aws-lambda-layer) to ensure the code uses the same tracer instance for all instrumentation.
-
-1. In your `.csproj` file, make sure the tracer version the project is built with matches the tracer version installed in the tracing layer. See Datadog Lambda tracing layer for .NET [release notes](https://github.com/DataDog/dd-trace-dotnet-aws-lambda-layer/releases) to determine which version of the Datadog tracer is packaged with your layer version.
-2. Compile your Lambda function as normal.
-3. Locate the packaged zip file. The Datadog tracer dll file must be removed. To do so, unzip, remove the tracer, and re-zip the package. The Datadog tracer file will be named something like `Datadog.Trace.dll`.
-4. Deploy your code as normal.
-
 ## Configure the Datadog tracer
 
 To see what libraries and frameworks are automatically instrumented by the Datadog APM client, see [Compatibility Requirements for APM][15]. To instrument custom applications, see Datadog's APM guide for [custom instrumentation][16].

content/en/serverless/aws_lambda/installation/dotnet.md

@@ -313,6 +313,15 @@ To use the optimized extension, disable Application Security Management (ASM), C
 
 Enabling any of these features cause the extension to default back to the fully compatible older version of the extension. You can also force your extension to use the older version by setting `DD_EXTENSION_VERSION` to `compatibility`. Datadog encourages you to report any feedback or bugs by adding an [issue on GitHub][8] and tagging your issue with `version/next`.
 
+## Adding Custom Spans
+
+Special care must be taken when installing the Datadog tracer when also using the [Datadog Lambda tracing layer for .NET](https://github.com/DataDog/dd-trace-dotnet-aws-lambda-layer) to ensure the code uses the same tracer instance for all instrumentation.
+
+1. In your `.csproj` file, make sure the tracer version the project is built with matches the tracer version installed in the tracing layer. See Datadog Lambda tracing layer for .NET [release notes](https://github.com/DataDog/dd-trace-dotnet-aws-lambda-layer/releases) to determine which version of the Datadog tracer is packaged with your layer version.
+2. Compile your Lambda function as normal.
+3. Locate the packaged zip file. The Datadog tracer dll file must be removed. To do so, unzip, remove the tracer, and re-zip the package. The Datadog tracer file will be named something like `Datadog.Trace.dll`.
+4. Deploy your code as normal.
+
 ## What's next?
 - You can now view metrics, logs, and traces on the [Serverless Homepage][1].
 - Turn on [threat monitoring][6] to get alerted on attackers targeting your service.