fix grammar issues

Author: claire-chan

barcode-reader/general/scan-specific-page.md

@@ -10,4 +10,4 @@ needAutoGenerateSidebar: false
 
 We are planning to add `Pages` parameter of the `ImageParameterOptions` Parameter.
 
-Currently you will need to manually filter out the extra results from the returned retults or you can convert the specific pages pdf file to single image files and then decode the images.
+Currently you will need to manually filter out the extra results from the returned results or you can convert the specific pages pdf file to single image files and then decode the images.

barcode-reader/mobile/capabilities/armv7-architecture-error.md

@@ -8,10 +8,10 @@ needAutoGenerateSidebar: true
 
 # How can I solve the "Undefined symbols for architecture armv7" error when building on iOS?
 
-DBR iOS is compatible with the arm64 and x86_64 architectures only. If you attempt to build an app that is targetting the armv7 architecture, you will be met with an error from the Barcode Reader framework saying
+DBR iOS is compatible with the arm64 and x86_64 architectures only. If you attempt to build an app that is targeting the armv7 architecture, you will be met with an error from the Barcode Reader framework saying
 
 > Undefined symbols for architecture armv7
 
 Please note that this will mostly occur with older versions of Xcode or iOS that are still compatible with the older iOS device models that used the armv7 architecture. For most devices that are able to run iOS 11 and higher, the architecture will be arm64.
 
-By default, when you set the *Architectures* in *Build Settings* to the "$(ARCHS_STANDARD) - Standard Architectures (arm64)", the armv7 architecture should automaticallt not be included. To ensure that your app ignores the armv7 architecture, you can add it to the *Excluded Architectures* field of the *Build Settings*.
+By default, when you set the *Architectures* in *Build Settings* to the "$(ARCHS_STANDARD) - Standard Architectures (arm64)", the armv7 architecture should automatically not be included. To ensure that your app ignores the armv7 architecture, you can add it to the *Excluded Architectures* field of the *Build Settings*.

barcode-reader/server/configuration/custom-settings-template.md

@@ -8,7 +8,7 @@ needAutoGenerateSidebar: false
 
 ## How to create custom settings template?
 
-One of the strengths of the Dynamsoft Barcode Reader is its wide range of cuztomizable options that can optimize the performance of the SDK. Whether you are looking to prioritize read rate or speed, these settings can be used in many ways to match the targeted use case.
+One of the strengths of the Dynamsoft Barcode Reader is its wide range of customizable options that can optimize the performance of the SDK. Whether you are looking to prioritize read rate or speed, these settings can be used in many ways to match the targeted use case.
 
 If you are looking to create your own custom template of settings to use with the [InitSettingsFromFile][https://www.dynamsoft.com/capture-vision/docs/server/programming/cplusplus/api-reference/capture-vision-router/settings.html?product=dbr&repoType=server#initsettingsfromfile] methods, here are the steps:
 

barcode-reader/server/configuration/non-english-characters.md

@@ -1,12 +1,12 @@
 ---
 layout: default-layout
-title: What I can do when barcode image returnes messy (non-english) characters?
+title: What I can do when barcode image returns messy (non-english) characters?
 keywords: Dynamsoft Barcode Reader, FAQ, DBR Introduction, messy characters, non-English characters
-description: What I can do when barcode image returnes messy (non-english) characters?
+description: What I can do when barcode image returns messy (non-english) characters?
 needAutoGenerateSidebar: false
 ---
 
-## What I can do when barcode image returnes messy (non-english) characters?
+## What I can do when barcode image returns messy (non-english) characters?
 
 The barcode text of the result is of a non-Latin based language, as by default most webpages are able to display Latin-based languages.
 

barcode-reader/web/capabilities/is-https-required.md

@@ -10,6 +10,6 @@ needAutoGenerateSidebar: false
 
 HTTPS is required to utilize `getUserMedia`/`MediaDevices` and initialize online license keys. If HTTPS is not enabled, you won't be able to use a camera and you will need an offline license key.
 
-> 1. If you don't want to use a camera, you can enable [singleFrameMode](https://www.dynamsoft.com/barcode-reader/programming/javascript/api-reference/BarcodeScanner/properties.html?ver=latest#singleframemode) to scan barcodes on exisiting images.
+> 1. If you don't want to use a camera, you can enable [singleFrameMode](https://www.dynamsoft.com/barcode-reader/programming/javascript/api-reference/BarcodeScanner/properties.html?ver=latest#singleframemode) to scan barcodes on existing images.
 > 2. During evaluation & testing, you can use 'http://localhost' which allows camera usage as well as online licensing.
 

barcode-reader/web/configuration/get-intermediate-result-images.md

@@ -9,7 +9,7 @@ needAutoGenerateSidebar: false
 # How to get intermediate result images?
 
 ## Version 10 and above
-The intermeddiate results can be retrieved using the [IntermediateResultManager]({{ site.dcvb_js_api }}capture-vision-router/intermediate-result-manager.html)
+The intermediate results can be retrieved using the [IntermediateResultManager]({{ site.dcvb_js_api }}capture-vision-router/intermediate-result-manager.html)
 
 
 ## Version 9

barcode-reader/web/scan-setting/differences-between-full-and-compact-editions.md

@@ -12,7 +12,7 @@ needAutoGenerateSidebar: false
 
 The main difference between the two is the set of supported barcode formats as well as the size of each edition. For the full list of differences between the two, please refer to this [article](https://www.dynamsoft.com/barcode-reader/programming/javascript/user-guide/features-requirements.html#compact-and-full-editions).
 
-**Compact edition** supports `1D`, `QR`, `PDF417`, and `Datamatrix` (the most popular barcode formats), while the **full edition** supports the complete set of Dynamsoft Barcode Reader's supported barcode formats.
+**Compact edition** supports `1D`, `QR`, `PDF417`, and `DataMatrix` (the most popular barcode formats), while the **full edition** supports the complete set of Dynamsoft Barcode Reader's supported barcode formats.
 In terms of API methods, the full edition supports the following features while the compact does not: `getIntermediateCanvas`, `initRuntimeSettingsWithString`, and ` outputSettingsToString`.
 
 As a result of that, the **compact edition** is smaller in size compared to the full edition, offering a slightly faster compilation time when the user first uses the application. Using the **compact edition** can also help in reducing the size of the compiled *wasm*.

license/track-license.md

@@ -4,12 +4,11 @@ title: How to track the number of devices?
 keywords: Dynamsoft Barcode Reader, FAQ, Pricing/Licensing, General, track license
 description: How to track the number of devices?
 needAutoGenerateSidebar: false
-: faq/general/track-license.html
 ---
 
 ## How to track the number of devices?
 
 The Dynamsoft License Server (Dynamsoft hosted or self-hosted) is able to keep a track of the number of devices in different ways, depending on the edition of the SDK.
 
-- On the browser (JS Edition), a device is counted as a specific browser on that device. This license gets cached in the indexedDB of the browser. If another browser is used, or the indexedDB is cleared, then a new license seat is taken up by the same device.
+- On the browser (JavaScript Edition), a device is counted as a specific browser on that device. This license gets cached in the indexedDB of the browser. If another browser is used, or the indexedDB is cleared, then a new license seat is taken up by the same device.
 - With other editions of the SDK, a local license is assigned to the device that is identified by a UUID, which is unique to each device.