Clarify logging category behavior and environment variable limitations for ILogger in Linux hosting

Author: ggailey777

articles/azure-functions/dotnet-isolated-process-guide.md

@@ -829,11 +829,7 @@ public class MyFunction {
 ```
 
 > [!NOTE]
-> Loggers obtained through dependency injection are associated with a log category set to the fully qualified name of the class.
-> This usually consists in a category name with one or more `.` (period) characters.
-> When hosting your function app on Linux App Service plans, please be aware of
-> [limitations with category names that contain a dot](/dotnet/core/extensions/logging?tabs=bash#set-log-level-by-command-line-environment-variables-and-other-configuration). You will not be able to override
-> log levels for those categories using environment variables.
+> When you inject an `ILogger<T>` in your class constructor, like the previous example, the log category is automatically set to the fully qualified name of that class, such as `MyFunctionApp.MyFunction`. These category names contain `.` (period) characters. When you host your function app on Linux, you can't use environment variables to override log levels for categories that contain periods. To work around this limitation, you can instead [configure log levels in your code](#managing-log-levels) or in an `appsettings.json` file.
 
 You can also get the logger from a [FunctionContext] object passed to your function. Call the [GetLogger&lt;T&gt;] or [GetLogger] method, passing a string value that is the name for the category in which the logs are written. The category is usually the name of the specific function from which the logs are written. For more information about categories, see the [monitoring article](functions-monitoring.md#log-levels-and-categories).