Merge pull request #318 from microsoft/pete-dev

docu
microsoft · Apr 17, 2024 · 3a053c7 · 3a053c7
2 parents f2c57b5 + e89bdee
commit 3a053c7
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 10 deletions.
diff --git a/docs/index.md b/docs/index.md
@@ -1,7 +1,7 @@
 ---
 title: Windows Midi Services
 layout: home
-has_children: true
+has_children: false
 ---
 # Windows MIDI Services
 

diff --git a/docs/troubleshooting/type-initialization-error.md b/docs/troubleshooting/type-initialization-error.md
@@ -4,14 +4,8 @@ title: Type Initialization Error at Runtime
 parent: Troubleshooting
 ---
 
-# Troubleshooting
+# Type Initializer Error
 
-## Errors
-
-
-### Type Initializer Error
-
-If you receive the error "The type initializer for `Windows.Devices.Midi2.<some class>` threw an exception", in the console app in particular, it usually means that the Windows MIDI Services API is not properly registered on the system. This can happen during development if you do run the installer which puts the appropriate activation entries into the registry.
-
-This should never appear in production when Windows MIDI Services is in the box, unless you are using a development build for which the newer types have not been properly registered.
+If you receive the error "The type initializer for `Windows.Devices.Midi2.<some class>` threw an exception" at runtime, in the console app in particular, it usually means that the Windows MIDI Services API is not properly registered on the system. This can happen during development if you don't run the installer which puts the appropriate activation entries into the registry.
 
+This should never appear in production when Windows MIDI Services is in Windows, unless you are using a development build for which the newer types have not been properly registered.