Update 8.0.md

Fix style issues

conceptual/Npgsql/release-notes/8.0.md

@@ -71,15 +71,16 @@ To allow Npgsql to write command batches containing large data payloads (general
 Affected APIs are the synchronous command execution methods: ExecuteReader, ExecuteNonQuery, ExecuteScalar in combination with a command batch (i.e. NpgsqlBatch or semicolon ';' concatenated commands).
 
 If you are affected by this you can consider some of the following options:
-- Use [ThreadPool.SetMinThreads()](https://learn.microsoft.com/en-us/dotnet/api/system.threading.threadpool.setminthreads?view=net-8.0) to expand the minimum pool of threads available for blocking.
-- Refactor code using command batches to use asynchronous apis.
 
-If these options are not suitable for your project you can consider opening an issue on https://github.com/npgsql/npgsql. This helps us prioritize the effort to bring back some mitigation in a patch version.
+* Use [ThreadPool.SetMinThreads()](https://learn.microsoft.com/en-us/dotnet/api/system.threading.threadpool.setminthreads?view=net-8.0) to expand the minimum pool of threads available for blocking.
+* Refactor code using command batches to use asynchronous apis.
+
+If these options are not suitable for your project you can consider opening an issue on [https://github.com/npgsql/npgsql](https://github.com/npgsql/npgsql). This helps us prioritize the effort to bring back some mitigation in a patch version.
 
 To clarify, Npgsql 8.0 has not dropped support for synchronous command batches completely; the feature is entirely supported for use at low load or for local data exploration.
 
-Note:
-We recommend using the asynchronous APIs for all scenarios. 
+Note: 
+We recommend using the asynchronous APIs for all scenarios.  
 Going forward existing and new functionality will see a reduced focus on having the synchronous API surface be as complete or as supported as its asynchronous counterpart. This is in line with broader .NET trends, including many modern building blocks — that would otherwise be useful to Npgsql — only support asynchronous use.
 
 For 9.0 or later we're considering disabling synchronous I/O by default (see [https://github.com/npgsql/npgsql/issues/5865](https://github.com/npgsql/npgsql/issues/5865)). Add your comment there, describing your use-case, if you believe this change would force you to stay on an older version.