Skip to content

Commit e5018a7

Browse files
committed
Edits
1 parent dab9855 commit e5018a7

File tree

3 files changed

+4
-4
lines changed

3 files changed

+4
-4
lines changed

articles/healthcare-apis/iot/how-to-use-mapping-debugger.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ In this article, you'll learn how to use the MedTech service Mapping debugger in
3737
- **FHIR destination mapping**: The FHIR destination mapping currently used by your MedTech service.
3838
- **Mappings**: Both mappings currently used by your MedTech service
3939

40-
## How to troubleshoot using the Mapping debugger
40+
## How to troubleshoot the device and FHIR destination mappings using the Mapping debugger
4141

4242
1. If there are errors with the device or FHIR destination mappings, the Mapping debugger will display the issues. In this example, we can see that there are error *warnings* at **Line 12** in the **Device mapping** and at **Line 20** in the **FHIR destination mapping**.
4343

articles/healthcare-apis/iot/index.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -55,9 +55,9 @@ landingContent:
5555
links:
5656
- text: Mapping debugger
5757
url: how-to-use-mapping-debugger.md
58-
- text: Device mappings
58+
- text: Device mapping
5959
url: how-to-configure-device-mappings.md
60-
- text: FHIR destination mappings
60+
- text: FHIR destination mapping
6161
url: how-to-configure-fhir-mappings.md
6262

6363
- title: Monitor the MedTech service

articles/healthcare-apis/iot/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ items:
4444
- name: Mapping debugger
4545
expanded: false
4646
items:
47-
- name: Mapping debugger
47+
- name: Use the Mapping debugger
4848
href: how-to-use-mapping-debugger.md
4949
- name: Device
5050
expanded: false

0 commit comments

Comments
 (0)