From b9db60356828f3e808d8917b800d2de65518922b Mon Sep 17 00:00:00 2001 From: Kshithij Iyer Date: Mon, 12 Aug 2019 16:08:08 +0530 Subject: [PATCH] Fixing markdown errors in op_version.md --- docs/Upgrade-Guide/op_version.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/Upgrade-Guide/op_version.md b/docs/Upgrade-Guide/op_version.md index 9eefe98..46af8e9 100644 --- a/docs/Upgrade-Guide/op_version.md +++ b/docs/Upgrade-Guide/op_version.md @@ -1,12 +1,12 @@ -###op-version +### op-version op-version is the operating version of the Gluster which is running. op-version was introduced to ensure gluster running with different versions do not end up in a problem and backward compatibility issues can be tackled. After Gluster upgrade, it is advisable to have op-version updated. -###Updating op-version +### Updating op-version Current op-version can be queried as below: @@ -32,7 +32,7 @@ For example, after upgrading to glusterfs-4.0.0, set op-version as: Note: This is not mandatory, but advisable to have updated op-version if you want to make use of latest features in the updated gluster. -###Client op-version +### Client op-version When trying to set a volume option, it might happen that one or more of the connected clients cannot support the feature being set and might need to be upgraded to the op-version the cluster is currently running on.