docs: move note section content

Author: filzrev

docs/articles/features/disassembler.md

@@ -17,18 +17,6 @@ The configuration options available from code level are:
 * `exportCombinedDisassemblyReport`: Exports all benchmarks to a single HTML report. Makes it easy to compare different runtimes or methods (each becomes a column in HTML table).
 * `exportDiff`: Exports a diff of the assembly code to the Github markdown format. False by default.
 
-The configuration options available for MSBuild properties:
-
-* `BenchmarkDotNetTargetPlatform`: Specify `all` to include all native dependencies of disassembler.
-
-> [!NOTE]
-> By default, BenchmarkDotNet excludes disassembler's native dependencies that aren't used on current target platform.  
-> Use the following settings when running the benchmark binary on a different platform than it was built on, or multiple platforms.
->
-> ```xml
-> <BenchmarkDotNetTargetPlatform>all</BenchmarkDotNetTargetPlatform>
-> ```
-
 ### Requirements
 
 Disassembly Diagnoser requires following settings in your `.csproj` file:
@@ -45,6 +33,14 @@ To get the source code we need to locate and read the `.pdb` files.
 This is why we need `DebugType` and `DebugSymbols` settings.
 To compare different platforms the project which defines benchmarks has to target `AnyCPU`.
 
+> [!NOTE]
+> By default, BenchmarkDotNet excludes disassembler's native dependencies that aren't used on current target platform.  
+> Use the following settings when running the benchmark binary on a different platform than it was built on, or multiple platforms.
+>
+> ```xml
+> <BenchmarkDotNetTargetPlatform>all</BenchmarkDotNetTargetPlatform>
+> ```
+
 ### Disassembly Diagnoser for Mono on Windows
 
 If you want to get a disassembly listing for Mono on Windows, you need `as` and `x86_64-w64-mingw32-objdump.exe` tools.