update tutorials formatting

Signed-off-by: dbulahov <[email protected]>

Author: dbulahov

docs/cubeserver/tutorial/complex.school.md

@@ -8,10 +8,10 @@ number: 2.4.4
 
 This tutorial discusses roles with CatalogGrant.
 
-`roleAll` role                   : use CatalogGrant access `all`; (access `cube1`)<br />
-`roleNone` role                  : use CatalogGrant access `none`; (no access `cube1`)<br />
-`roleAllDimWithCubeGrand` role   : use CatalogGrant access `all_dimensions`; CubeGrant `cube1` access all; `cube2` access none (access `cube1`)<br />
-`roleAllDimWithoutCubeGrand` role: use CatalogGrant access `all_dimensions` without cube grant (As result is 'no access'. For access need CubeGrant with `custom` or `all`)<br />;
+- `roleAll` role                   : use CatalogGrant access `all`; (access `cube1`)
+- `roleNone` role                  : use CatalogGrant access `none`; (no access `cube1`)
+- `roleAllDimWithCubeGrand` role   : use CatalogGrant access `all_dimensions`; CubeGrant `cube1` access all; `cube2` access none (access `cube1`)
+- `roleAllDimWithoutCubeGrand` role: use CatalogGrant access `all_dimensions` without cube grant (As result is 'no access'. For access need CubeGrant with `custom` or `all`)
 
 
 ## Database Schema
@@ -163,22 +163,22 @@ This files represent the complete definition of the catalog.
       <measures xsi:type="roma:SumMeasure" id="_measure_sum" name="Measure1" column="_column_fact_value"/>
     </measureGroups>
   </roma:PhysicalCube>
-  <roma:AccessRole id="_accessRole_none" name="roleNone">
-    <accessCatalogGrants/>
+  <roma:AccessRole id="_accessRole_allDimWithCubeGrand" name="roleAllDimWithCubeGrand">
+    <accessCatalogGrants catalogAccess="all_dimensions">
+      <cubeGrants cubeAccess="all" cube="_cube_main"/>
+    </accessCatalogGrants>
   </roma:AccessRole>
   <roma:AccessRole id="_accessRole_all" name="roleAll">
     <accessCatalogGrants catalogAccess="all"/>
   </roma:AccessRole>
+  <roma:AccessRole id="_accessRole_none" name="roleNone">
+    <accessCatalogGrants/>
+  </roma:AccessRole>
   <roma:AccessRole id="_accessRole_allDimWithoutCubeGrand" name="roleAllDimWithoutCubeGrand">
     <accessCatalogGrants catalogAccess="all_dimensions">
       <databaseSchemaGrants databaseSchemaAccess="all" databaseSchema="_databaseSchema_CatalogGrand"/>
     </accessCatalogGrants>
   </roma:AccessRole>
-  <roma:AccessRole id="_accessRole_allDimWithCubeGrand" name="roleAllDimWithCubeGrand">
-    <accessCatalogGrants catalogAccess="all_dimensions">
-      <cubeGrants cubeAccess="all" cube="_cube_main"/>
-    </accessCatalogGrants>
-  </roma:AccessRole>
 </xmi:XMI>
 
 ```

docs/cubeserver/tutorial/tutorial.access.cataloggrand.md

@@ -8,8 +8,8 @@ number: 2.4.3
 
 This tutorial discusses roles with ColumnGrant.
 
-roleAll    role: use TableGrant access all; (access all database all tables all columns)<br />
-roleNone   role: use TableGrant access none; (no access to database columns)<br />
+- `roleAll`    role: use TableGrant access `all`; (access all database all tables all columns)
+- `roleNone`   role: use TableGrant access `none`; (no access to database columns)
 
 
 ## Database Schema
@@ -111,23 +111,23 @@ This files represent the complete definition of the catalog.
       <measures xsi:type="roma:SumMeasure" id="_measure_sum" name="Measure1" column="_column_fact_value"/>
     </measureGroups>
   </roma:PhysicalCube>
-  <roma:AccessRole id="_accessRole_all" name="roleAll">
+  <roma:AccessRole id="_accessRole_none" name="roleNone">
     <accessCatalogGrants catalogAccess="all">
       <cubeGrants cubeAccess="all" cube="_cube_main"/>
       <databaseSchemaGrants databaseSchemaAccess="custom" databaseSchema="_databaseSchema_ColumnGrand">
         <tableGrants tableAccess="custom" table="_table_fact">
-          <columnGrants columnAccess="all" column="_column_fact_value"/>
-          <columnGrants columnAccess="all" column="_column_fact_key"/>
+          <columnGrants column="_column_fact_value"/>
         </tableGrants>
       </databaseSchemaGrants>
     </accessCatalogGrants>
   </roma:AccessRole>
-  <roma:AccessRole id="_accessRole_none" name="roleNone">
+  <roma:AccessRole id="_accessRole_all" name="roleAll">
     <accessCatalogGrants catalogAccess="all">
       <cubeGrants cubeAccess="all" cube="_cube_main"/>
       <databaseSchemaGrants databaseSchemaAccess="custom" databaseSchema="_databaseSchema_ColumnGrand">
         <tableGrants tableAccess="custom" table="_table_fact">
-          <columnGrants column="_column_fact_value"/>
+          <columnGrants columnAccess="all" column="_column_fact_value"/>
+          <columnGrants columnAccess="all" column="_column_fact_key"/>
         </tableGrants>
       </databaseSchemaGrants>
     </accessCatalogGrants>

docs/cubeserver/tutorial/tutorial.access.columngrand.md

@@ -8,13 +8,13 @@ number: 2.4.5
 
 This tutorial discusses roles with with CubeGrant.
 
-role1 role:   use CubeGrant cube1 access all; cube2 access none (access cube1)
+- `role1` role:   use CubeGrant cube1 access `all`; cube2 access `none` (access `cube1`)
 
 
 
 ## Database Schema
 
-The Database Schema contains the Fact table with two columns: KEY and VALUE. The KEY column is used as the discriminator in the the Level and Hierarchy definitions.
+The Database Schema contains the `Fact` table with two columns: `KEY` and `VALUE`. The `KEY` column is used as the discriminator in the the Level and Hierarchy definitions.
 
 
 ```xml
@@ -29,7 +29,7 @@ The Database Schema contains the Fact table with two columns: KEY and VALUE. The
 *<small>Note: This is only a symbolic example. For the exact definition, see the [Definition](#definition) section.</small>*
 ## Query
 
-The Query is a simple TableQuery that selects all columns from the Fact table to use in in the hierarchy and in the cube for the measures.
+The Query is a simple TableQuery that selects all columns from the `Fact` table to use in in the hierarchy and in the cube for the measures.
 
 
 ```xml
@@ -39,7 +39,7 @@ The Query is a simple TableQuery that selects all columns from the Fact table to
 *<small>Note: This is only a symbolic example. For the exact definition, see the [Definition](#definition) section.</small>*
 ## Level1
 
-This Example uses one simple Level1 bases on the KEY column.
+This Example uses one simple Level1 bases on the `KEY` column.
 
 
 ```xml
@@ -69,7 +69,7 @@ The dimension1 is defined with the one hierarchy1.
 *<small>Note: This is only a symbolic example. For the exact definition, see the [Definition](#definition) section.</small>*
 ## Cube1 with access all
 
-The cube1 is defines by the DimensionConnector1 and the DimensionConnector2  and the MeasureGroup with measure with aggregation sum.
+The `cube1` is defines by the DimensionConnector1 and the DimensionConnector2  and the MeasureGroup with measure with aggregation sum.
 
 
 ```xml
@@ -85,7 +85,7 @@ The cube1 is defines by the DimensionConnector1 and the DimensionConnector2  and
 *<small>Note: This is only a symbolic example. For the exact definition, see the [Definition](#definition) section.</small>*
 ## Cube2 with access none
 
-The cube2 is defines by the DimensionConnector1 and the MeasureGroup with measure with aggregation sum.
+The `cube2` is defines by the DimensionConnector1 and the MeasureGroup with measure with aggregation sum.
 
 
 ```xml
@@ -98,7 +98,7 @@ The cube2 is defines by the DimensionConnector1 and the MeasureGroup with measur
 *<small>Note: This is only a symbolic example. For the exact definition, see the [Definition](#definition) section.</small>*
 ## Role1
 
-The role1 use CatalogGrant access all_dimensions; CubeGrant cube1 access all; cube2 access none (access cube1)
+The `role1` use CatalogGrant access all_dimensions; CubeGrant `cube1` access `all`; cube2 access `none` (access cube1)
 
 
 ```xml
@@ -131,17 +131,17 @@ This files represent the complete definition of the catalog.
   <roma:TableQuery id="_query_factQuery" table="_table_fact"/>
   <roma:Level id="_level_Level1" name="Level1" column="_column_fact_key"/>
   <roma:StandardDimension id="_dimension_Dimension1" name="Dimension1" hierarchies="_hierarchy_Hierarchy1"/>
-  <roma:PhysicalCube id="_cube_Cube2" name="Cube2" query="_query_factQuery">
-    <dimensionConnectors foreignKey="_column_fact_key" dimension="_dimension_Dimension1" overrideDimensionName="Dimension1" id="_dimensionConnector_dimension1"/>
-    <measureGroups/>
-  </roma:PhysicalCube>
   <roma:PhysicalCube id="_cube_Cube1" name="Cube1" query="_query_factQuery">
     <dimensionConnectors foreignKey="_column_fact_key" dimension="_dimension_Dimension1" overrideDimensionName="Dimension1" id="_dimensionConnector_dimension11"/>
     <dimensionConnectors foreignKey="_column_fact_key" dimension="_dimension_Dimension1" overrideDimensionName="Dimension2" id="_dimensionConnector_dimension12"/>
     <measureGroups>
       <measures xsi:type="roma:SumMeasure" id="_measure_Measure1" name="Measure1" column="_column_fact_value"/>
     </measureGroups>
   </roma:PhysicalCube>
+  <roma:PhysicalCube id="_cube_Cube2" name="Cube2" query="_query_factQuery">
+    <dimensionConnectors foreignKey="_column_fact_key" dimension="_dimension_Dimension1" overrideDimensionName="Dimension1" id="_dimensionConnector_dimension1"/>
+    <measureGroups/>
+  </roma:PhysicalCube>
   <roma:AccessRole id="_accessRole_role1" name="role1">
     <accessCatalogGrants catalogAccess="all_dimensions">
       <cubeGrants cubeAccess="all" cube="_cube_Cube1"/>

docs/cubeserver/tutorial/tutorial.access.cubegrand.md

@@ -8,8 +8,8 @@ number: 2.4.1
 
 This tutorial discusses roles with with DatabaseSchemaGrant.
 
-`roleAll` role : use DatabaseSchemaGrant access `all`; (access all database)<br />
-`roleNone` role: use CatalogGrant access `none`; (no access to database)<br />
+- `roleAll` role : use DatabaseSchemaGrant access `all`; (access all database)
+- `roleNone` role: use CatalogGrant access `none`; (no access to database)
 
 
 ## Database Schema

docs/cubeserver/tutorial/tutorial.access.databaseschemagrand.md

@@ -8,13 +8,13 @@ number: 2.4.6
 
 This tutorial discusses roles with DimensionGrant.
 
-`role1` role:   use DimensionGrant access to `Dimension1` and not access to `Dimension2` of `cube1`
+- `role1` role:   use DimensionGrant access to `Dimension1` and not access to `Dimension2` of `cube1`
 
 
 
 ## Database Schema
 
-The Database Schema contains the `Fact` table with two columns: KEY and VALUE. The KEY column is used as the discriminator in the the Level and Hierarchy definitions.
+The Database Schema contains the `Fact` table with two columns: `KEY` and `VALUE`. The `KEY` column is used as the discriminator in the the Level and Hierarchy definitions.
 
 
 ```xml
@@ -39,7 +39,7 @@ The Query is a simple TableQuery that selects all columns from the `Fact` table
 *<small>Note: This is only a symbolic example. For the exact definition, see the [Definition](#definition) section.</small>*
 ## Level1
 
-This Example uses one simple Level1 bases on the KEY column.
+This Example uses one simple Level1 bases on the `KEY` column.
 
 
 ```xml
@@ -49,7 +49,7 @@ This Example uses one simple Level1 bases on the KEY column.
 *<small>Note: This is only a symbolic example. For the exact definition, see the [Definition](#definition) section.</small>*
 ## Hierarchy1 without hasAll Level1
 
-The Hierarchy1 is defined with the hasAll property set to false and the one level1.
+The Hierarchy1 is defined with the hasAll property set to false and the one `level1`.
 
 
 ```xml
@@ -59,7 +59,7 @@ The Hierarchy1 is defined with the hasAll property set to false and the one leve
 *<small>Note: This is only a symbolic example. For the exact definition, see the [Definition](#definition) section.</small>*
 ## Dimension1
 
-The dimension1 is defined with the one hierarchy1.
+The `dimension1` is defined with the one `hierarchy1`.
 
 
 ```xml
@@ -69,7 +69,7 @@ The dimension1 is defined with the one hierarchy1.
 *<small>Note: This is only a symbolic example. For the exact definition, see the [Definition](#definition) section.</small>*
 ## Cube1 with access all
 
-The cube1 is defines by the DimensionConnector1 and the DimensionConnector2  and the MeasureGroup with measure with aggregation sum.
+The `cube1` is defines by the DimensionConnector1 and the DimensionConnector2  and the MeasureGroup with measure with aggregation sum.
 
 
 ```xml
@@ -85,7 +85,7 @@ The cube1 is defines by the DimensionConnector1 and the DimensionConnector2  and
 *<small>Note: This is only a symbolic example. For the exact definition, see the [Definition](#definition) section.</small>*
 ## Role1
 
-The `role1` use CatalogGrant access `all_dimensions`; CubeGrant cube1 access `all`; cube2 access `none` (access cube1)
+The `role1` use CatalogGrant access `all_dimensions`; CubeGrant `cube1` access `all`; `cube2` access `none` (access `cube1`)
 
 
 ```xml

docs/cubeserver/tutorial/tutorial.access.dimensiongrand.md

@@ -8,7 +8,7 @@ number: 2.4.7
 
 This tutorial discusses role with HierarchyGrant
 
-`role1` role:   use HierarchyGrant hierarchy1 access `all` hierarchy2 access `none`;
+- `role1` role:   use HierarchyGrant hierarchy1 access `all` hierarchy2 access `none`;
 
 
 ## Database Schema

docs/cubeserver/tutorial/tutorial.access.hierarchygrand.md

@@ -9,15 +9,15 @@ number: 2.4.8
 This tutorial discusses role with MemberGrant
 
 role1 role: with member grants <br />
-[Dimension1].[A] -all,<br />
-[Dimension1].[B] -none,<br />
-[Dimension1].[C] -none;<br />
+- [Dimension1].[A] -all;
+- [Dimension1].[B] -none;
+- [Dimension1].[C] -none;
 (Cube1 - access to 'A' only)
 
 Rollup policy: (Full. Partial. Hidden.)<br />
-Full. The total for that member includes all children. This is the default policy if you don't specify the rollupPolicy attribute.<br />
-Partial. The total for that member includes only accessible children.<br />
-Hidden. If any of the children are inaccessible, the total is hidden.<br />
+- Full. The total for that member includes all children. This is the default policy if you don't specify the rollupPolicy attribute.
+- Partial. The total for that member includes only accessible children.
+- Hidden. If any of the children are inaccessible, the total is hidden.
 
 
 ## Database Schema

docs/cubeserver/tutorial/tutorial.access.membergrand.md

@@ -8,9 +8,9 @@ number: 2.4.2
 
 This tutorial discusses roles with TableGrant.
 
-`roleAll`    role: use TableGrant access `all`; (access all database all tables)<br />
-`roleNone`   role: use TableGrant access `none`; (no access to database tables)<br />
-`roleCustom` role: use TableGrant access `custom`; (access to database table Fact)<br />
+- `roleAll`    role: use TableGrant access `all`; (access all database all tables)<br />
+- `roleNone`   role: use TableGrant access `none`; (no access to database tables)<br />
+- `roleCustom` role: use TableGrant access `custom`; (access to database table Fact)<br />
 
 
 ## Database Schema