diff --git a/xml/System/AppDomain.xml b/xml/System/AppDomain.xml
index ed06b0d16f1..232fc86dadc 100644
--- a/xml/System/AppDomain.xml
+++ b/xml/System/AppDomain.xml
@@ -91,7 +91,6 @@
 Application domains, which are represented by <xref:System.AppDomain> objects, help provide isolation, unloading, and security boundaries for executing managed code.
 
 - Use application domains to isolate tasks that might bring down a process. If the state of the <xref:System.AppDomain> that's executing a task becomes unstable, the <xref:System.AppDomain> can be unloaded without affecting the process. This is important when a process must run for long periods without restarting. You can also use application domains to isolate tasks that should not share data.
-
 - If an assembly is loaded into the default application domain, it cannot be unloaded from memory while the process is running. However, if you open a second application domain to load and execute the assembly, the assembly is unloaded when that application domain is unloaded. Use this technique to minimize the working set of long-running processes that occasionally use large DLLs.
 
  > [!NOTE]
@@ -5804,9 +5803,8 @@ This method overload uses the <xref:System.AppDomainSetup> information from the
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- The friendly name of the default application domain is the file name of the process executable. For example, if the executable used to start the process is `"c:\MyAppDirectory\MyAssembly.exe"`, the friendly name of the default application domain is `"MyAssembly.exe"`.
-
 
+The friendly name of the default application domain is the file name of the process executable. For example, if the executable used to start the process is `"c:\MyAppDirectory\MyAssembly.exe"`, the friendly name of the default application domain is `"MyAssembly.exe"`. (In .NET Core and .NET 5+, the friendly name doesn't include the file extension.)
 
 ## Examples
  The following code example uses the <xref:System.AppDomain.FriendlyName%2A> property to get the friendly name of the current application domain. For the default application domain, the friendly name is the name of the application's executable file. The code example also displays additional information about the application domain.