i1153 additional fixes

eclipse-che · Jul 19, 2019 · 0fb3b22 · 0fb3b22
1 parent d5400ef
commit 0fb3b22
Show file tree

Hide file tree

Showing 3 changed files with 16 additions and 17 deletions.
diff --git a/...-on-guidance/proc_adding-the-vs-code-extension-using-the-che-plugins-panel.adoc b/...-on-guidance/proc_adding-the-vs-code-extension-using-the-che-plugins-panel.adoc
@@ -23,11 +23,11 @@
 [id="adding-the-vs-code-extension-using-the-che-plugins-panel_{context}"]
 = Adding the VS Code extension using the Che Plugins panel
 
-To add the VS Code extension using the *Che Plugin* panel, follow the procedure below.
-
 [discrete]
 == Procedure
 
+To add the VS Code extension using the *Che Plugin* panel, follow the procedure below.
+
 . Open the *Che Plugin* panel.
 
 . Change the current registry to the registry in which the VS Code extension was added.
@@ -36,5 +36,5 @@ To add the VS Code extension using the *Che Plugin* panel, follow the procedure
 +
 image::extensibility/adding_the_vs_code_extension_changeRegistry.png[]
 
-. Search for the required plug-in using the filter and then click the *Install* button.
+. Search for the required plug-in using the filter and then click the btn:[Install] button.
 . Restart the workspace for the changes to take effect.
diff --git a/...nds-on-guidance/proc_importing-a-vs-code-extension-in-the-che-theia-editor.adoc b/...nds-on-guidance/proc_importing-a-vs-code-extension-in-the-che-theia-editor.adoc
@@ -31,7 +31,7 @@ This method of installing the VS Code extensions is aimed at extensions that do
 [discrete]
 == Prerequisites
 
-* Configure the Che Theia memory limit with 512 MB RAM or more to run the Theia editor. In addition, reserve another 512 MB RAM for the VS Code extensions.
+* Configure the Che Theia memory limit with 512 MB RAM or more to run the Theia editor. In addition, reserve sufficient memory for the VS code extensions. The specific amount of memory required depends on the extensions used.
 
 [discrete]
 == Procedure

diff --git a/...guidance/proc_writing-a-meta-yaml-file-and-adding-it-to-a-plug-in-registry.adoc b/...guidance/proc_writing-a-meta-yaml-file-and-adding-it-to-a-plug-in-registry.adoc
@@ -37,20 +37,19 @@ The plug-in meta information is required to publish a VS Code extension in an Ec
 
 [source,yaml]
 --
-apiVersion: `v3`        <1>
-publisher: `myorg`      <2>
-name: `my-vscode-ext`	<3>
-version: `1.7.2`        <4>
-type:                   <5>
-displayName: 	        <6>
-title: 			<7>
-description: 		<8>
-icon: `https://www.eclipse.org/che/images/logo-eclipseche.svg`	<9>
-repository: 		<10>
-category: 		<11>
+apiVersion: `v3`                                                 <1>
+publisher: `myorg`                                               <2>
+name: `my-vscode-ext`	                                    <3>
+version: `1.7.2`                                                 <4>
+type:name: value                                                 <5>
+displayName: 	                                            <6>
+title: 			                                  <7>
+description: 		                                    <8>
+icon: `https://www.eclipse.org/che/images/logo-eclipseche.svg`   <9>
+repository: 		                                    <10>
+category: 		                                      <11>
 spec:
-
-  containers: # If this section is omitted, the VS Code extension is added into the Che Theia IDE container
+containers: # If this section is omitted, the VS Code extension is added into the Che Theia IDE container
     - image: The Docker image from which the sidecar container will be started. Example: "eclipse/che-theia-endpoint-runtime:next"
       memoryLimit: The RAM which is given for the sidecar container by default. Example: "256Mi". This value might be overridden by the user in the component configuration.
   extensions: A list of VA Code extensions that should be run in this sidecar container. Example: