Skip to content

Commit 885e1b2

Browse files
committed
minor edit
1 parent 0908fff commit 885e1b2

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

articles/azure-resource-manager/bicep/bicep-functions-date.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ The datetime value that results from adding the duration value to the base value
3232

3333
### Remarks
3434

35-
The `dateTimeAdd` function doesn't take leap years into consideration, and _P1Y_ should be interpreted as _P365D_, while _P1M_ should be interpreted as P30D. The following json shows some examples:
35+
The `dateTimeAdd` function doesn't take leap years into consideration, and _P1Y_ should be interpreted as _P365D_, while _P1M_ should be interpreted as _P30D_. The following Bicep file shows some examples:
3636

3737
```bicep
3838
output addOneYearNonLeap string = dateTimeAdd('2023-01-01 00:00:00Z', 'P1Y') //2024-01-01T00:00:00Z

articles/azure-resource-manager/templates/template-functions-date.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ The datetime value that results from adding the duration value to the base value
3535

3636
### Remarks
3737

38-
The `dateTimeAdd` function doesn't take leap years into consideration, and _P1Y_ should be interpreted as _P365D_, while _P1M_ should be interpreted as P30D. The following json shows some examples:
38+
The `dateTimeAdd` function doesn't take leap years into consideration, and _P1Y_ should be interpreted as _P365D_, while _P1M_ should be interpreted as _P30D_. The following json shows some examples:
3939

4040
```json
4141
{

0 commit comments

Comments
 (0)