fixes to markdown files for Flare migration

Author: PeninaR

site/content/xap/12.3/admin/gigaspaces-browser-menus-and-buttons.markdown

@@ -158,7 +158,7 @@ The **Help** menu provides the following options
 
 The button toolbar allows you to perform maintenance operations on containers and spaces.
 
-|Syntax|Description|
+|Button|Description|
 |:-----|:----------|
 | ![ping.gif](/attachment_files/ping.gif) | Pings the selected space |
 | ![clean_space.gif](/attachment_files/clean_space.gif) | Cleans the selected space |

site/content/xap/12.3/admin/gigaspaces-browser-tree-panel-and-configuration-panel.markdown

@@ -15,15 +15,14 @@ The left hand panel of the Space Browser is the **Grid Tree**. This panel allows
 ![IMG212.gif](/attachment_files/IMG212.gif)
 {{% /align %}}
 
-{{%section%}}
-{{%column width="5%" %}}
-![cluster_node.gif](/attachment_files/cluster_node.gif)
-{{%/column%}}
-{{%column width="95%" %}}
-The **Grid Tree** shows the following main types of nodes:
-{{%/column%}}
-{{%/section%}}
+The **Grid Tree** shows the following main types of nodes.
 
+|Icon|Description|
+|:-----|:----------|
+| ![space_network_view_icon.gif](/attachment_files/space_network_view_icon.gif) | Root of the Spaces grid tree. |
+| ![container.gif](/attachment_files/container.gif) | Space Container node. |
+| ![spaceTreeIcon.gif](/attachment_files/spaceTreeIcon.gif) | Space node. |
+| ![cluster_node.gif](/attachment_files/cluster_node.gif) | Cluster node. |
 
 # Spaces Network View
 
@@ -100,7 +99,7 @@ You can choose to refresh the Space Network view periodically. Select the desire
 
 # Space Container Node
 
-|![container.gif](/attachment_files/container.gif) | Right-clicking a space container node (invokes a context menu containing the following options:
+Right-clicking a Space container node invokes a context menu containing the following options:
 
 {{% align center %}}
 ![grid_tree_containerNodeSelected_6.5.jpg](/attachment_files/grid_tree_containerNodeSelected_6.5.jpg)
@@ -118,14 +117,7 @@ Selecting the space container node also makes available the three leftmost butto
 
 {{% anchor spacenode %}}
 
-{{%section%}}
-{{%column width="5%" %}}
-![spaceTreeIcon.gif](/attachment_files/spaceTreeIcon.gif)
-{{%/column%}}
-{{%column width="95%" %}}
 Space nodes represent a single space in the system.
-{{%/column%}}
-{{%/section%}}
 
 **The space node has five possible views:**
 
@@ -153,23 +145,13 @@ When a space node is selected, its configuration data is displayed in the **Serv
 
 # Cluster Node
 
-{{%section%}}
-{{%column width="5%" %}}
-![cluster_node.gif](/attachment_files/cluster_node.gif)
-{{%/column%}}
-{{%column width="95%" %}}
-
 A cluster is a collection of spaces from one or more space containers. The cluster node in the **Grid Tree** represents a cluster of spaces.
 
 {{% refer %}}
 For more details, refer to the [Cluster View](./cluster-view-gigaspaces-browser.html) section.
 {{%/refer%}}
 
-{{%/column%}}
-{{%/section%}}
-
-
-# Service View panel
+# Service View Panel
 
 The **Service View** panel takes up most of the Space Browser screen; it is located on the right of the **Grid Tree** panel. This panel shows configuration details for the node selected in the tree on the left, allowing you to edit some of them.
 

site/content/xap/12.3/admin/the-runtime-environment.markdown

@@ -17,33 +17,29 @@ To start a Service Grid on a machine, launch the `gs-agent` utility located in t
 ## Help
 Run gs-agent with `--help` or `-h` to see all available options:
 
-{{% section %}}
-{{% column width="50%" %}}
-**Linux**
+{{%tabs%}}
+{{% tab Linux %}}
 
 ```bash
 ./gs-agent.sh --help
 ```
 
-{{% /column %}}
-
-{{% column width="45%" %}}
-**Windows**
+{{%/tab%}}
+{{% tab Windows %}}
 
 ```bash
 gs-agent --help
 ```
 
-{{% /column %}}
-{{% /section %}}
+{{% /tab %}}
+{{% /tabs %}}
 
 ## Manager
 
 To start a single manager on the local machine (useful for dev and testing):
 
-{{% section %}}
-{{% column width="50%" %}}
-**Linux**
+{{%tabs%}}
+{{% tab Linux %}}
 
 ```bash
 # Starts a local manager:
@@ -52,10 +48,8 @@ To start a single manager on the local machine (useful for dev and testing):
 ./gs-agent.sh --manager-local --gsc=2
 ```
 
-{{% /column %}}
-
-{{% column width="45%" %}}
-**Windows**
+{{%/tab%}}
+{{% tab Windows %}}
 
 ```bash
 REM Starts a local manager:
@@ -64,14 +58,13 @@ REM Starts a local manager and 2 GSCs:
 gs-agent --manager-local --gsc=2
 ```
 
-{{% /column %}}
-{{% /section %}}
+{{% /tab %}}
+{{% /tabs %}}
 
 To start a highly-available cluster of managers on several hosts, run the following on each of the designated hosts:
 
-{{% section %}}
-{{% column width="50%" %}}
-**Linux**
+{{%tabs%}}
+{{% tab Linux %}}
 
 ```bash
 # Starts a manager:
@@ -80,10 +73,8 @@ To start a highly-available cluster of managers on several hosts, run the follow
 ./gs-agent.sh --manager --gsc=2
 ```
 
-{{% /column %}}
-
-{{% column width="45%" %}}
-**Windows**
+{{%/tab%}}
+{{% tab Windows %}}
 
 ```bash
 REM Starts a manager:
@@ -92,18 +83,17 @@ REM Starts a manager and 2 GSCs:
 gs-agent --manager --gsc=2
 ```
 
-{{% /column %}}
-{{% /section %}}
+{{% /tab %}}
+{{% /tabs %}}
 
 (Note that you also need to configure the `XAP_MANAGER_SERVERS` to the list of designated manager servers)
 
 ## Without Manager
 
 If you cannot use the manager for some reason, but you still want high-availability, you can pick a couple of hosts to serve for management, and start a LUS and GSM on them:
 
-{{% section %}}
-{{% column width="50%" %}}
-**Linux**
+{{%tabs%}}
+{{% tab Linux %}}
 
 ```bash
 # Starts a LUS and GSM:
@@ -112,10 +102,8 @@ If you cannot use the manager for some reason, but you still want high-availabil
 ./gs-agent.sh --lus --gsm --gsc=2
 ```
 
-{{% /column %}}
-
-{{% column width="45%" %}}
-**Windows**
+{{%/tab%}}
+{{% tab Windows %}}
 
 ```bash
 REM Starts a LUS and GSM:
@@ -124,54 +112,48 @@ REM Starts a LUS, GSM and 2 GSCs:
 gs-agent --lus --gsm --gsc=2
 ```
 
-{{% /column %}}
-{{% /section %}}
+{{% /tab %}}
+{{% /tabs %}}
 
 Alternatively, if your environment supports multicast and you prefer a more dynamic approach, you can use the `global` prefix to indicate that GSMs and LUSs will be automatically started and managed by the collective of gs-agents, instead of explicitly on a specific hosts. For example, to start 2 Global GSM and LUS accross a set of hosts, as well as 2 GSCs on each host:
 
-{{% section %}}
-{{% column width="50%" %}}
-**Linux**
+{{%tabs%}}
+{{% tab Linux %}}
 
 ```bash
 # Starts a LUS, GSM and 2 GSCs:
 ./gs-agent.sh --global.lus=2 --global.gsm=2 --gsc=2
 ```
 
-{{% /column %}}
-
-{{% column width="45%" %}}
-**Windows**
+{{%/tab%}}
+{{% tab Windows %}}
 
 ```bash
 REM Starts a LUS, GSM and 2 GSCs:
 gs-agent --global.lus=2 --global.gsm=2 --gsc=2
 ```
 
-{{% /column %}}
-{{% /section %}}
+{{% /tab %}}
+{{% /tabs %}}
 
 In fact, since this configuration is convenient for new users, it is also the default - running `gs-agent` without any arguments would produce the same effect. If you wish to disable it and start without any components, run gs-agent with `--zero-defaults` or `-z`. This can be useful if you're planning to use the  manager's RESTful API from another host to add/remove containers.
 
-{{% section %}}
-{{% column width="50%" %}}
-**Linux**
+{{%tabs%}}
+{{% tab Linux %}}
 
 ```bash
 ./gs-agent.sh -z
 ```
 
-{{% /column %}}
-
-{{% column width="45%" %}}
-**Windows**
+{{%/tab%}}
+{{% tab Windows %}}
 
 ```bash
 gs-agent -z
 ```
 
-{{% /column %}}
-{{% /section %}}
+{{% /tab %}}
+{{% /tabs %}}
 
 # Configuration
 
@@ -187,9 +169,8 @@ The component-specific configuration override the system-wide configuration.
 
 For example:
 
-{{% section %}}
-{{% column width="50%" %}}
-**Linux**
+{{%tabs%}}
+{{% tab Linux %}}
 
 ```bash
 export XAP_GSA_OPTIONS=-Xmx256m
@@ -200,10 +181,8 @@ export XAP_LUS_OPTIONS=-Xmx1g
 ./gs-agent.sh
 ```
 
-{{% /column %}}
-
-{{% column width="45%" %}}
-**Windows**
+{{%/tab%}}
+{{% tab Windows %}}
 
 ```bash
 set XAP_GSA_OPTIONS=-Xmx256m
@@ -214,8 +193,8 @@ set XAP_LUS_OPTIONS=-Xmx1g
 call gs-agent.bat
 ```
 
-{{% /column %}}
-{{% /section %}}
+{{% /tab %}}
+{{% /tabs %}}
 
 # Customizing GSA Components
 

site/content/xap/12.3/dev-dotnet/interoperability-of-user-defined-objects.markdown

@@ -22,11 +22,8 @@ Properties mapping: when defining interoperability of properties the names of th
 
 For the purpose of explaining the subject we'll look at a Person class (a deep class)
 
-
-
-{{%section%}}
-{{%column width="50%" %}}
-**C#**
+{{%tabs%}}
+{{% tab "C#" %}}
 
 ```csharp
 using GigaSpaces.Core.Metadata;
@@ -69,11 +66,8 @@ namespace MyCompany.MyProject.Entities
 }
 ```
 
-{{%/column%}}
-
-{{%column width="50%" %}}
-**Java**
-
+{{%/tab%}}
+{{% tab Java %}}
 
 ```java
 package com.mycompany.myproject.entities;
@@ -99,7 +93,7 @@ public class Address
 }
 ```
 
-{{%/column%}}
-{{%/section%}}
+{{% /tab %}}
+{{% /tabs %}}
 
 

site/content/xap/12.3/dev-dotnet/interoperability.markdown

@@ -12,9 +12,8 @@ XAP supports easy and efficient communication and access across projects that in
 
 # Designing Interoperable Classes
 
-{{%section%}}
-{{%column width="50%" %}}
- C#
+{{%tabs%}}
+{{% tab "C#" %}}
 
 ```csharp
 using GigaSpaces.Core.Metadata;
@@ -35,10 +34,8 @@ namespace MyCompany.MyProject.Entities
 }
 ```
 
-{{%/column%}}
-
-{{%column width="50%" %}}
- Java
+{{%/tab%}}
+{{% tab Java %}}
 
 ```java
 package com.mycompany.myproject.entities;
@@ -60,8 +57,8 @@ package com.mycompany.myproject.entities;
 }
 ```
 
-{{%/column%}}
-{{%/section%}}
+{{% /tab %}}
+{{% /tabs %}}
 
 ## Guidelines and Restrictions
 

site/content/xap/12.3/dev-java/jpa-api-overview.markdown

@@ -364,7 +364,7 @@ em.close();
 emf.close();
 ```
 
-**JOIN support for one to many relationship (Owner --> List<Pet>)**
+**JOIN support for one to many relationship (Owner --> List&lt;Pet&gt;)**
 
 
 ```java