Merge branch 'microsoft:main' into main

content/docs/BestPractices/CustomTelemetry/index.md

@@ -71,7 +71,7 @@ Of course it is possible to have a single object as a central place to emit tele
 
 ## Candidate data for telemetry
 
-Telemetry must be **actionable** for the customer. Do not emit signals that they cannot act on (knowing about CPU performance counters on the database is useless if the partner cannot scale the database)
+Telemetry must be **actionable** for the customer. Do not emit signals that they cannot act on (knowing about CPU performance counters on the database is useless if the partner cannot scale the database).
 
 Also, note that customers pay for data ingestion. So be mindful to not flood their telemetry resources. Consider to use TelemetryScope::ExtensionPublisher by default and only use TelemetryScope::All in case the customer can also act on the data.
 

content/docs/BestPractices/api-page/index.md

@@ -166,7 +166,7 @@ It is common use to give certain fields a more describing name. Some examples ar
 These fields should always be part of the API Page:
 
 * SystemId
-  * This field should be exposed wit the name ```id```  
+  * This field should be exposed with the name ```id```
 * SystemModifiedAt
   * This field should be exposed with the name ```lastModifiedDateTime```. If you choose a different name, then the webhook functionality will not work properly.
 
@@ -179,8 +179,8 @@ layout
     {
         repeater(records)
         {
-            field(id; SystemId) { }
+            field(id; Rec.SystemId) { }
-            field(lastModifiedDateTime; SystemModifiedAt) { }
+            field(lastModifiedDateTime; Rec.SystemModifiedAt) { }
         }
     }
 }

content/docs/BestPractices/begin-as-an-afterword/index.md

@@ -15,7 +15,7 @@ When `begin` follows `then`, `else`, `do`, it should be on the same line, preced
 ```al
     if ICPartnerRefType = ICPartnerRefType::"Common Item No." then
     begin
-    ...
+        ...
     end;
 ```
 
@@ -23,7 +23,6 @@ When `begin` follows `then`, `else`, `do`, it should be on the same line, preced
 
 ```al
     if ICPartnerRefType = ICPartnerRefType::"Common Item No." then begin
-    ...
+        ...
     end;
 ```
-

content/docs/BestPractices/begin-end/index.md

@@ -13,7 +13,7 @@ Only use begin..end to enclose [compound statements](https://docs.microsoft.com/
 ```AL
 if FindSet() then begin
     repeat
-    ...
+        ...
     until next() = 0;
 end;
 ```
@@ -23,7 +23,7 @@ end;
 ```AL
 if FindSet() then
     repeat
-    ...
+        ...
     until next() = 0;
 ```
 
@@ -52,4 +52,3 @@ if X then begin
 end else 
     (not X)
 ```
-

content/docs/BestPractices/binary-operator-line-start/index.md

@@ -14,14 +14,14 @@ Do not start a line with a binary operator.
 
 ```AL
 "Quantity to Ship" :=
-Quantity 
+    Quantity 
-- "Quantity Shipped"
+    - "Quantity Shipped"
 ```
 
 ## Good code
 
 ```AL
 "Quantity to Ship" :=
-Quantity -
+    Quantity -
-"Quantity Shipped"
+    "Quantity Shipped"
 ```

content/docs/BestPractices/end-else-pair/index.md

@@ -15,11 +15,11 @@ The `end else` pair should always appear on the same line.
 ```al
     if OppEntry.Find('-') then
         if SalesCycleStage.Find('-') then begin
-        ...
+            ...
         end
         else
         begin
-        ... 
+            ... 
         end;
 ```
 
@@ -28,8 +28,8 @@ The `end else` pair should always appear on the same line.
 ```al
     if OppEntry.Find('-') then
         if SalesCycleStage.Find('-') then begin
-        ...
+            ...
         end else begin
-        ...
+            ...
         end;
 ```

content/docs/BestPractices/separate-if-and-else/index.md

@@ -13,15 +13,15 @@ _Created by Microsoft, Described by waldo_
 ## Bad code
 
 ```al
-    if Atom = '\>' then HasLogicalOperator := true else begin
+    if Atom = '>' then HasLogicalOperator := true else begin
-    ...
+        ...
     end;
 ```
 
 ## Good code
 
 ```al
-    if Atom = '\>' then
+    if Atom = '>' then
         HasLogicalOperator := true
     else begin
         ...