From 201e62813f9e960351b2aa6202eb90758077268c Mon Sep 17 00:00:00 2001
From: Alena Prokharchyk <alena@rancher.com>
Date: Mon, 3 Jun 2019 13:52:39 -0700
Subject: [PATCH] Update _index.md

---
 content/rke/latest/en/config-options/_index.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/content/rke/latest/en/config-options/_index.md b/content/rke/latest/en/config-options/_index.md
index b1ad9fa6f07..a2c7f7c5649 100644
--- a/content/rke/latest/en/config-options/_index.md
+++ b/content/rke/latest/en/config-options/_index.md
@@ -92,17 +92,17 @@ If you want to use a different version from the supported list, please use the [
 
 ### Prefix Path
 
-For some operating systems including ROS, and CoreOS, RKE stores its resources to a different prefix path, this prefix path is by default for these operating systems is:
-```
-/opt/rke
-```
-So `/etc/kubernetes` will be stored in `/opt/rke/etc/kubernetes` and `/var/lib/etcd` will be stored in `/opt/rke/var/lib/etcd` etc.
+As a part of cluster provisioning, RKE uploads config files' content - `/etc/kubernetes`,`/var/lib/etcd`, etc - to the worker nodes. By default, these configs get stored under `/`. 
+For some operating systems like RancherOS and CoreOS, the location is `/opt/rke` instead of `/`. With that, `/etc/kubernetes` will be stored in `/opt/rke/etc/kubernetes`, `/var/lib/etcd` will be stored in `/opt/rke/var/lib/etcd`, and so on.
+
+To change the default prefix path for any type of cluster, you can use the following option in the cluster configuration file `cluster.yml`:
 
-To change the default prefix path for any cluster, you can use the following option in the cluster configuration file `cluster.yml`:
 ```
 prefix_path: /opt/custom_path
 ```
 
+#### **Important: currently there is a limitation when `prefix_path` can not be changed or reset after the cluster is provisioned**
+
 ### Cluster Level SSH Key Path
 
 RKE connects to host(s) using `ssh`. Typically, each node will have an independent path for each ssh key, i.e. `ssh_key_path`, in the `nodes` section, but if you have a SSH key that is able to access **all** hosts in your cluster configuration file, you can set the path to that ssh key at the top level. Otherwise, you would set the ssh key path in the [nodes]({{< baseurl >}}/rke/latest/en/config-options/nodes/).