docs: fix layout #2425 (#2433)

docs/admin/developer/agama/dsl-full.md

@@ -335,24 +335,24 @@ y = ...
 z = [ 3.1416, 2.71828 ]
 
 Match car.model to
-    x
-        //Code in this block will be executed if car.model is equal to the value of x
-       ...
+   x
+      //Code in this block will be executed if car.model is equal to the value of x
+      ...
 
-    -y //Here we use minus y
-       ...  
+   -y //Here we use minus y
+      ...  
 
-    z[0]
-       ...
+   z[0]
+      ...
 
-    1.618 //Literal values can be used too for matching
-       ...  
+   1.618 //Literal values can be used too for matching
+      ...  
 
-    null
-        ...
+   null
+      ...
 
 Otherwise    //optional block
-    //Instructions here are executed if there was no match at all 
+   //Instructions here are executed if there was no match at all 
 ```
 
 ## Flow finish
@@ -472,7 +472,7 @@ result = RFAC map.twitter.loginUrl
 ```
 
 </td>
-		<td>Redirects to the given location. Once the user browser is taken to the callback URL by the external site, the data included in the query string or payload is stored in <code>result</code> (a _map_) for further processing</td>
+		<td>Redirects to the given location. Once the user browser is taken to the callback URL by the external site, the data included in the query string or payload is stored in <code>result</code> (a map) for further processing</td>
 	</tr>
 </table>
 
@@ -938,15 +938,17 @@ x["1"]
 ```
 
 </td>
-<td>
+</tr><tr>
+<td colspan="3">
 
 ```
 x[ z[0] ]
 //illegal: variable expressions not allowed for indexes 
 ```
 
 </td>
-<td>
+</tr><tr>
+<td colspan="3">
 
 ```
 x[obj.property]

docs/admin/developer/agama/quick-start.md

@@ -191,10 +191,10 @@ This usually boils down to create and launch a URL looking like `https://<your-h
 
 - To trigger an Agama flow, the `acr_values` parameter must be equal to `agama`
 
-- The qualified name (identifier) of the flow to trigger is passed using the parameter referenced via property `cust_param_name` of the Agama bridge script. `customParam1` will work in most installations since this is the default value employed in the script. For the current example `customParam1=test` should be fine
+- The qualified name (identifier) of the flow to trigger is passed using the parameter referenced in property `cust_param_name` of the Agama bridge script. `customParam1` will work in most cases since this is the default value employed by the Jans installer. For the current example `customParam1=test` should be fine
 
 !!! Note
-    To use a different parameter ensure to register the given parameter in the [server configuration](../../config-guide/jans-cli/im/im-jans-authorization-server.md) (property `authorizationRequestCustomAllowedParameters`) and update the bridge accordingly
+    To use a different parameter name ensure to register the given parameter in the [server configuration](../../config-guide/jans-cli/im/im-jans-authorization-server.md) (property `authorizationRequestCustomAllowedParameters`) and update the bridge accordingly
 
 - If the flow to call receives input parameters, their values can be passed in the custom parameter as well. Use a hyphen to separate the flow name and the parameters expressed in JSON object format. For example, if the flow had inputs  `height` and `color`, you can use `test-{"height": 190, "color": "blue"}` for the value of `customParam1`. Ensure to apply proper URL-encoding beforehand. In this case, the actual value would be `test-%7B%22height%22%3A+190%2C+%22color%22%3A+%22blue%22%7D`. If certain inputs are not provided, `null` values will be assigned for them