Fix docs bug

Signed-off-by: Aadhitya A <aadhitya864@gmail.com>

docs/pages/project/contributing/contributing-cli.md

@@ -165,8 +165,7 @@ Example:```
 mesheryctl system start
 
 // To create a new context for in-cluster Kubernetes deployments and set the new context as your current-context
-mesheryctl system context create k8s -p kubernetes -s
-```,
+mesheryctl system context create k8s -p kubernetes -s```,
 Annotations: linkScreenshot,
 ...{% endcapture %}
 
@@ -186,8 +185,7 @@ Example:```
 mesheryctl pattern apply -f [file | URL]
 
 // deploy a saved pattern
-mesheryctl pattern apply [pattern-name]
-```,
+mesheryctl pattern apply [pattern-name]```,
 Annotations: linkDocPatternApply,
 ...
 {% endcapture %}
@@ -222,7 +220,6 @@ If your mesheryctl docs end like this, add the include tag at the end of the fil
 
 {% raw %}{% include permalink-of-file %}{% endraw %}
 {% endcapture %}
-{% include mesheryctl/code.html code=code_content %}
 
 
 This format should reference an external file where your manual changes are stored. These files should be present at the folder path (`_includes/mesheryctl/`). Any content added using this method will not be altered during the documentation generation process, but instead will be included post-auto doc generation. When making new changes or additions, understand that these additional details are positioned at the end their given CLI reference page, so bear this in mind as you organize and present your additional command details.