diff --git a/guides/protocols/odata.md b/guides/protocols/odata.md index 958480c72c..a09f2edad7 100644 --- a/guides/protocols/odata.md +++ b/guides/protocols/odata.md @@ -799,7 +799,7 @@ service S { In addition, the following functions are supported: -* `$Null()` representing the `null` value [`Null`]([annotation expression](#null-value)). +* `$Null()` representing the `null` value ([annotation expression](#null-value)). * `Div(...)` (or `$Div(...)`) and `Mod(...)` (or `$Mod(...)`) for integer division and modulo * [`Has(...)`](https://docs.oasis-open.org/odata/odata/v4.02/csd01/part2-url-conventions/odata-v4.02-csd01-part2-url-conventions.html#Has) (or `$Has(...)`) * the functions listed in sections diff --git a/node.js/databases.md b/node.js/databases.md index 365b63a8a6..ca6a4d7eb3 100644 --- a/node.js/databases.md +++ b/node.js/databases.md @@ -24,8 +24,8 @@ In case of database services this actually starts the transaction by acquiring a This method is called automatically by the framework on the first query, so **you never have to call it** in application coding. There are only very rare cases where you'd want to do so, for example to reuse a `tx` object to start subsequent physical transactions after a former `commit` or `rollback`. But this is not considered good practice. -## cds.DatabaseService — Consumption {#databaseservice-consumption } -###### databaseservice-consumption +## cds.DatabaseService — Consumption +##### databaseservice-consumption