[docs] Fix all typos in plugins typo. (#7129)

Signed-off-by: yanggang <gang.yang@daocloud.io>

site/content/docs/main/custom-plugins.md

@@ -37,7 +37,7 @@ When naming your plugin, keep in mind that the full name needs to conform to the
 - have two parts, prefix + name, separated by '/'
 - none of the above parts can be empty
 - the prefix is a valid DNS subdomain name
-- a plugin with the same prefix + name cannot not already exist
+- a plugin with the same prefix + name cannot already exist
 
 ### Some examples:
 

site/content/docs/v1.0.0/plugins.md

@@ -15,7 +15,7 @@ When naming your plugin, keep in mind that the name needs to conform to these ru
 - have two parts separated by '/'
 - none of the above parts can be empty
 - the prefix is a valid DNS subdomain name
-- a plugin with the same name cannot not already exist
+- a plugin with the same name cannot already exist
 
 ### Some examples:
 

site/content/docs/v1.1.0/plugins.md

@@ -15,7 +15,7 @@ When naming your plugin, keep in mind that the name needs to conform to these ru
 - have two parts separated by '/'
 - none of the above parts can be empty
 - the prefix is a valid DNS subdomain name
-- a plugin with the same name cannot not already exist
+- a plugin with the same name cannot already exist
 
 ### Some examples:
 

site/content/docs/v1.10/custom-plugins.md

@@ -37,7 +37,7 @@ When naming your plugin, keep in mind that the full name needs to conform to the
 - have two parts, prefix + name, separated by '/'
 - none of the above parts can be empty
 - the prefix is a valid DNS subdomain name
-- a plugin with the same prefix + name cannot not already exist
+- a plugin with the same prefix + name cannot already exist
 
 ### Some examples:
 

site/content/docs/v1.11/custom-plugins.md

@@ -37,7 +37,7 @@ When naming your plugin, keep in mind that the full name needs to conform to the
 - have two parts, prefix + name, separated by '/'
 - none of the above parts can be empty
 - the prefix is a valid DNS subdomain name
-- a plugin with the same prefix + name cannot not already exist
+- a plugin with the same prefix + name cannot already exist
 
 ### Some examples:
 

site/content/docs/v1.2.0/custom-plugins.md

@@ -15,7 +15,7 @@ When naming your plugin, keep in mind that the name needs to conform to these ru
 - have two parts separated by '/'
 - none of the above parts can be empty
 - the prefix is a valid DNS subdomain name
-- a plugin with the same name cannot not already exist
+- a plugin with the same name cannot already exist
 
 ### Some examples:
 

site/content/docs/v1.3.0/custom-plugins.md

@@ -15,7 +15,7 @@ When naming your plugin, keep in mind that the name needs to conform to these ru
 - have two parts separated by '/'
 - none of the above parts can be empty
 - the prefix is a valid DNS subdomain name
-- a plugin with the same name cannot not already exist
+- a plugin with the same name cannot already exist
 
 ### Some examples:
 

site/content/docs/v1.3.1/custom-plugins.md

@@ -15,7 +15,7 @@ When naming your plugin, keep in mind that the name needs to conform to these ru
 - have two parts separated by '/'
 - none of the above parts can be empty
 - the prefix is a valid DNS subdomain name
-- a plugin with the same name cannot not already exist
+- a plugin with the same name cannot already exist
 
 ### Some examples:
 

site/content/docs/v1.3.2/custom-plugins.md

@@ -15,7 +15,7 @@ When naming your plugin, keep in mind that the name needs to conform to these ru
 - have two parts separated by '/'
 - none of the above parts can be empty
 - the prefix is a valid DNS subdomain name
-- a plugin with the same name cannot not already exist
+- a plugin with the same name cannot already exist
 
 ### Some examples:
 

site/content/docs/v1.4/custom-plugins.md

@@ -15,7 +15,7 @@ When naming your plugin, keep in mind that the name needs to conform to these ru
 - have two parts separated by '/'
 - none of the above parts can be empty
 - the prefix is a valid DNS subdomain name
-- a plugin with the same name cannot not already exist
+- a plugin with the same name cannot already exist
 
 ### Some examples:
 

site/content/docs/v1.5/custom-plugins.md

@@ -37,7 +37,7 @@ When naming your plugin, keep in mind that the full name needs to conform to the
 - have two parts, prefix + name, separated by '/'
 - none of the above parts can be empty
 - the prefix is a valid DNS subdomain name
-- a plugin with the same prefix + name cannot not already exist
+- a plugin with the same prefix + name cannot already exist
 
 ### Some examples:
 

site/content/docs/v1.6/custom-plugins.md

@@ -37,7 +37,7 @@ When naming your plugin, keep in mind that the full name needs to conform to the
 - have two parts, prefix + name, separated by '/'
 - none of the above parts can be empty
 - the prefix is a valid DNS subdomain name
-- a plugin with the same prefix + name cannot not already exist
+- a plugin with the same prefix + name cannot already exist
 
 ### Some examples:
 

site/content/docs/v1.7/custom-plugins.md

@@ -37,7 +37,7 @@ When naming your plugin, keep in mind that the full name needs to conform to the
 - have two parts, prefix + name, separated by '/'
 - none of the above parts can be empty
 - the prefix is a valid DNS subdomain name
-- a plugin with the same prefix + name cannot not already exist
+- a plugin with the same prefix + name cannot already exist
 
 ### Some examples:
 

site/content/docs/v1.8/custom-plugins.md

@@ -37,7 +37,7 @@ When naming your plugin, keep in mind that the full name needs to conform to the
 - have two parts, prefix + name, separated by '/'
 - none of the above parts can be empty
 - the prefix is a valid DNS subdomain name
-- a plugin with the same prefix + name cannot not already exist
+- a plugin with the same prefix + name cannot already exist
 
 ### Some examples:
 

site/content/docs/v1.9/custom-plugins.md

@@ -37,7 +37,7 @@ When naming your plugin, keep in mind that the full name needs to conform to the
 - have two parts, prefix + name, separated by '/'
 - none of the above parts can be empty
 - the prefix is a valid DNS subdomain name
-- a plugin with the same prefix + name cannot not already exist
+- a plugin with the same prefix + name cannot already exist
 
 ### Some examples: