docs: improve clarity in createInstance usage description

Author: 2heal1

apps/website-new/docs/en/guide/runtime/runtime-api.mdx

@@ -12,13 +12,13 @@ Used to create ModuleFederation instance.
 
 * When to use `createInstance`?
 
-To ensure the uniqueness of the ModuleFederation instance, after the build plugin creates an instance, it will be stored in memory. The exported APIs all first obtain the ModuleFederation instance from memory and then call the APIs of the ModuleFederation instance. This is also why APIs like loadRemote can be used directly from the `@module-federation/enhanced/runtime` package and inherently understand what application container they are attached to.
+  To ensure the uniqueness of the ModuleFederation instance, after the build plugin creates an instance, it will be stored in memory. The exported APIs all first obtain the ModuleFederation instance from memory and then call the APIs of the ModuleFederation instance. This is also why APIs like loadRemote can be used directly from the `@module-federation/enhanced/runtime` package and inherently understand what application container they are attached to.
 
-This singleton pattern works for most scenarios, but in the following cases, you need to use `createInstance`:
+  This singleton pattern works for most scenarios, but in the following cases, you need to use `createInstance`:
 
-- No build plugin is used  (Only use runtime)
-- Multiple ModuleFederation instances need to be created with different configurations for each instance
-- You want to use ModuleFederation's partitioning feature to encapsulate corresponding APIs for use in other projects
+  - No build plugin is used  (Only use runtime)
+  - Multiple ModuleFederation instances need to be created with different configurations for each instance
+  - You want to use ModuleFederation's partitioning feature to encapsulate corresponding APIs for use in other projects
 
 * `createInstance` will not overwrite an existing instance. Each call will create a new instance.