Merge pull request #253630 from dramasamy/vnf-cpu

Update quickstarts-tenant-workload-deployment.md

Author: prmerger-automator[bot]

articles/operator-nexus/quickstarts-tenant-workload-deployment.md

@@ -37,8 +37,8 @@ Before you run the commands, you need to set several variables to define the con
 | NETWORK_INTERFACE_NAME     | The name of the L3 network interface for the virtual machine.                                         |
 | ADMIN_USERNAME             | The username for the virtual machine administrator.                                                   |
 | SSH_PUBLIC_KEY             | The SSH public key that is used for secure communication with the virtual machine.                    |
-| CPU_CORES                  | The number of CPU cores for the virtual machine (even number, max 44 vCPUs)                                         |
-| MEMORY_SIZE                | The amount of memory (in GB, max 224 GB) for the virtual machine.                                                 |
+| CPU_CORES                  | The number of CPU cores for the virtual machine (even number, max 46 vCPUs)                           |
+| MEMORY_SIZE                | The amount of memory (in GB, max 224 GB) for the virtual machine.                                     |
 | VM_DISK_SIZE               | The size (in GB) of the virtual machine disk.                                                         |
 | VM_IMAGE                   | The URL of the virtual machine image.                                                                 |
 | ACR_URL                    | The URL of the Azure Container Registry.                                                              |
@@ -105,9 +105,6 @@ az networkcloud virtualmachine create \
 
 After a few minutes, the command completes and returns information about the virtual machine. You've created the virtual machine. You're now ready to use them.
 
-> [!NOTE]
-> If each server has two CPU chipsets and each CPU chip has 28 cores, then with hyperthreading enabled (default), the CPU chip supports 56 vCPUs. With 8 vCPUs in each chip reserved for infrastructure (OS and agents), the remaining 48 are available for tenant workloads.
-
 ## Review deployed resources
 
 [!INCLUDE [quickstart-review-deployment-cli](./includes/virtual-machine/quickstart-review-deployment-cli.md)]