Fix spelling error (#43761)

Author: bsivanov

docs/framework/configure-apps/file-schema/trace-debug/performancecounters-element.md

@@ -50,7 +50,7 @@ None.
 
 Performance counters use a memory mapped file, or shared memory, to publish performance data.  The size of the shared memory determines how many instances can be used at once.  There are two types of shared memory: global shared memory and separate shared memory.  The global shared memory is used by all performance counter categories installed with the .NET Framework versions 1.0 or 1.1.  Performance counter categories installed with the .NET Framework version 2.0 use separate shared memory, with each performance counter category having its own memory.
 
-The size of global shared memory can be set only with a configuration file.  The default size is 524,288 byes, the maximum size is 33,554,432 bytes, and the minimum size is 32,768 bytes.  Since the global shared memory is shared by all processes and categories, the first creator specifies the size.  If you define the size in your application configuration file, that size is only used if your application is the first application that causes the performance counters to execute.  Therefore the correct location to specify the `filemappingsize` value is the Machine.config file.  Memory in the global shared memory cannot be released by individual performance counters, so eventually global shared memory is exhausted if a large number of performance counter instances with different names are created.
+The size of global shared memory can be set only with a configuration file.  The default size is 524,288 bytes, the maximum size is 33,554,432 bytes, and the minimum size is 32,768 bytes.  Since the global shared memory is shared by all processes and categories, the first creator specifies the size.  If you define the size in your application configuration file, that size is only used if your application is the first application that causes the performance counters to execute.  Therefore the correct location to specify the `filemappingsize` value is the Machine.config file.  Memory in the global shared memory cannot be released by individual performance counters, so eventually global shared memory is exhausted if a large number of performance counter instances with different names are created.
 
 For the size of separate shared memory, the DWORD FileMappingSize value in the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\\*\<category name>*\Performance is referenced first, followed by the value specified for the global shared memory in the configuration file. If the FileMappingSize value does not exist, then the separate shared memory size is set to one fourth (1/4) the global setting in the configuration file.