diff --git a/content/os/v1.x/en/installation/networking/interfaces/_index.md b/content/os/v1.x/en/installation/networking/interfaces/_index.md
index 7e4035fb339..e3563a5d1a8 100644
--- a/content/os/v1.x/en/installation/networking/interfaces/_index.md
+++ b/content/os/v1.x/en/installation/networking/interfaces/_index.md
@@ -78,9 +78,7 @@ rancher:
 
 In this example two physical NICs (with MACs `0c:c4:d7:b2:14:d2` and `0c:c4:d7:b2:14:d3`) are aggregated into a virtual one `bond0`.
 
-During the bootup process, ROS needs to run cloud-init. It automatically detects the data sources of cloud-init, but some data sources require a network connection. 
-So in cloud-init, we open `rancher.network.interfaces.eth*.dhcp=true` by default, this may affect the bonding NIC.
-There is a way to avoid this problem is to use `rancher.network.interfaces.eth*.dhcp=false` in the kernel cmdline to disable DHCP for all NICs.
+During the bootup process, RancherOS runs cloud-init. It automatically detects the data sources of cloud-init, but sometimes a data source requires a network connection. By default, in cloud-init, we open `rancher.network.interfaces.eth*.dhcp=true`, which may affect the bonding NIC. If you do not require the network connection for your data-source, use `rancher.network.interfaces.eth*.dhcp=false` in the kernel cmdline to disable DHCP for all NICs.
 
 ### VLANS