Skip to content

Commit 3d4dd78

Browse files
authored
Acrolinx fixes
1 parent 3a38ec5 commit 3d4dd78

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

articles/cyclecloud/how-to/use-spot-instances.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ For details about Spot eviction in Azure, see [Spot Eviction Policy](/azure/virt
7373

7474
**Q.** How are users notified of eviction?
7575

76-
**A.** After CycleCloud evicts a node, users see a log message in the CycleCloud UI’s event log for the cluster. Users can also register to receive an Event from CycleCloud via [Azure EventGrid](/azure/cyclecloud/how-to/event-grid) after a spot instance is evicted.
76+
**A.** After CycleCloud evicts a node, users see a log message in the CycleCloud UI’s event log for the cluster. Users can also register to receive an Event from CycleCloud via [Azure Event Grid](/azure/cyclecloud/how-to/event-grid) after a spot instance is evicted.
7777

7878
* Users can check for an eviction notification on the machine 30 seconds before eviction. For details on how to register for the event, see [Scheduled Events](/azure/virtual-machines/linux/scheduled-events#why-use-scheduled-events).
7979
* In general, treat eviction like pulling the plug on an on-premises machine. Handle it in the same ways.

articles/cyclecloud/how-to/user-access.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ If you grant a user authentication access through a shared permission, remove th
5757
5858
## Disable the built-in user management system
5959

60-
Every CycleCloud installation enables the built-in user management system by default. This setting applies to the entire installation. All clusters that the CycleCloud server manages have this setting enabled. To disable it, go to the **CycleCloud** section of the **Settings** page. The pop-up box has an option for **Node Authentication**. Select **Disabled** from the drop down to make sure the system doesn't create any local user accounts aside from the VM agent user.
60+
Every CycleCloud installation enables the built-in user management system by default. This setting applies to the entire installation. All clusters that the CycleCloud server manages have this setting enabled. To disable it, go to the **CycleCloud** section of the **Settings** page. The pop-up box has an option for **Node Authentication**. Select **Disabled** from the drop-down to make sure the system doesn't create any local user accounts aside from the VM agent user.
6161

6262
![Disable Node Authentication](~/articles/cyclecloud/images/node-auth-disabled.png)
6363

articles/cyclecloud/how-to/vm-security.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.author: doclayto
88

99
# Virtual machine security configuration
1010

11-
CycleCloud 8.5 supports creating Vms with a security type of either [Trusted Launch](https://go.microsoft.com/fwlink/?LinkId=2153371) or [Confidential](https://aka.ms/ConfidentialVM).
11+
CycleCloud 8.5 supports creating VMs with a security type of either [Trusted Launch](https://go.microsoft.com/fwlink/?LinkId=2153371) or [Confidential](https://aka.ms/ConfidentialVM).
1212

1313
> [!NOTE]
1414
> Using these features might come with some limitations. These limitations include not supporting backup, managed disks, and ephemeral OS disks. In addition, these features require specific images and VM sizes. For more information, see the documentation in the preceding links.

0 commit comments

Comments
 (0)