From 7daee2da9edf3346aa9cee4ec203c0242e14d5a6 Mon Sep 17 00:00:00 2001
From: Saeid Bostandoust <49065072+ssbostan@users.noreply.github.com>
Date: Fri, 4 Sep 2020 13:36:00 +0430
Subject: [PATCH] command correction

---
 content/os/v1.x/en/installation/boot-process/logging/_index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/os/v1.x/en/installation/boot-process/logging/_index.md b/content/os/v1.x/en/installation/boot-process/logging/_index.md
index 9a4e8966b92..ad370802db4 100644
--- a/content/os/v1.x/en/installation/boot-process/logging/_index.md
+++ b/content/os/v1.x/en/installation/boot-process/logging/_index.md
@@ -38,4 +38,4 @@ For example, on my current test system, I have set the kernel boot line to:
 printk.devkmsg=on console=tty1 rancher.autologin=tty1 console=ttyS0 rancher.autologin=ttyS0    rancher.state.dev=LABEL=RANCHER_STATE rancher.state.autoformat=[/dev/sda,/dev/vda] rancher.rm_usr loglevel=8 netconsole=+9999@10.0.2.14/,514@192.168.42.223/
 ```
 
-The kernel boot parameters can be set during installation using `sudo ros install --append "...."`, or on an installed RancherOS system,  by running `sudo ros config syslinx` (which will start vi in a container, editing the `global.cfg` boot config file.
+The kernel boot parameters can be set during installation using `sudo ros install --append "...."`, or on an installed RancherOS system,  by running `sudo ros config syslinux` (which will start vi in a container, editing the `global.cfg` boot config file.