Skip to content

fix: correct phrasing in remarks for consistency across documentation #92

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Justin-dynamsoft merged 1 commit into from
Jul 14, 2026
Merged

fix: correct phrasing in remarks for consistency across documentation #92

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ...g/javascript/api-reference/capture-vision-router/intermediate-result-manager.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -126,7 +126,7 @@ await router.removeAllResultReceivers();

**Remarks**

New added in CaptureVisionBundle version 3.4.2000 & BarcodeReaderBundle version 11.4.2000.
Added in CaptureVisionBundle version 3.4.2000 & BarcodeReaderBundle version 11.4.2000.

### getOriginalImage

Expand Down
4 changes: 2 additions & 2 deletions ...ing/javascript/api-reference/capture-vision-router/multiple-image-processing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -322,7 +322,7 @@ router.removeAllResultReceivers();

**Remarks**

New added in CaptureVisionBundle version 3.4.2000 & BarcodeReaderBundle version 11.4.2000.
Added in CaptureVisionBundle version 3.4.2000 & BarcodeReaderBundle version 11.4.2000.

## addResultFilter

Expand Down Expand Up @@ -420,7 +420,7 @@ await router.removeAllResultFilters();

**Remarks**

New added in CaptureVisionBundle version 3.4.2000 & BarcodeReaderBundle version 11.4.2000.
Added in CaptureVisionBundle version 3.4.2000 & BarcodeReaderBundle version 11.4.2000.

## startCapturing

Expand Down
2 changes: 1 addition & 1 deletion programming/javascript/api-reference/identity-utility/identity-processor.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,4 +45,4 @@ if (quad) {

**Remarks**

New added in CaptureVisionBundle version 3.4.2000.
Added in CaptureVisionBundle version 3.4.2000.
2 changes: 1 addition & 1 deletion ...ming/javascript/api-reference/identity-utility/identity-utility-module-class.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,4 +37,4 @@ console.log(version);

**Remarks**

New added in CaptureVisionBundle version 3.4.2000.
Added in CaptureVisionBundle version 3.4.2000.
8 changes: 4 additions & 4 deletions programming/javascript/user-guide/mrz-scanner.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
layout: default-layout
title: Scan & Parse MRZ - Dynamsoft Capture Vision JavaScript Edition
description: This page introduce how to use Dynamsoft Capture Vision JS edition to recognize the Machine-Readable Zone (MRZ) on a passport or ID card and converts the encoded strings into human-readable fields.
description: This page introduces how to use Dynamsoft Capture Vision JS edition to recognize the Machine-Readable Zone (MRZ) on a passport or ID card and converts the encoded strings into human-readable fields.
keywords: JavaScript, scan mrz, read mrz, scan passport, read passport, scan id mrz, read id mrz
needAutoGenerateSidebar: true
needGenerateH3Content: true
Expand Down Expand Up @@ -272,9 +272,9 @@ Dynamsoft.Core.CoreModule.engineResourcePaths.rootDirectory = "https://cdn.jsdel

*Note*:

* Certain legacy web application servers may lack support for the `application/wasm` mimetype for .wasm files. To address this, you have two options:
1. Upgrade your web application server to one that supports the `application/wasm` mimetype.
2. Manually define the mimetype on your server. You can refer to the following resources for guidance:
* Certain legacy web application servers may lack support for the `application/wasm` MIME type for .wasm files. To address this, you have two options:
1. Upgrade your web application server to one that supports the `application/wasm` MIME type.
2. Manually define the MIME type on your server. You can refer to the following resources for guidance:
1. [Apache](https://developer.mozilla.org/en-US/docs/Learn/Server-side/Apache_Configuration_htaccess#media_types_and_character_encodings){:target="_blank"}
2. [IIS](https://docs.microsoft.com/en-us/iis/configuration/system.webserver/staticcontent/mimemap){:target="_blank"}
3. [Nginx](https://www.nginx.com/resources/wiki/start/topics/examples/full/#mime-types){:target="_blank"}
Expand Down