You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -81,11 +81,11 @@ sbt +publishLocal
81
81
82
82
### Details about the implementation using `regexes.yaml` file
83
83
84
-
This project use the 'regexes.yaml' file from [ua-parser/uap-core](https://github.com/ua-parser/uap-core/) repository to
84
+
This project uses the 'regexes.yaml' file from [ua-parser/uap-core](https://github.com/ua-parser/uap-core/) repository to
85
85
perform user-agent string parsing according to the [documented specification](https://github.com/ua-parser/uap-core/blob/master/docs/specification.md).
86
86
The file is included as a git submodule in the `core` directory.
87
87
88
-
Bellow, follows a summary of that same specification.
88
+
Below, follows a summary of that same specification.
89
89
90
90
#### Summary
91
91
@@ -164,8 +164,8 @@ Similarly, OS rules map:
164
164
Devices are slightly different: if no replacements are given, the first match defines the device family and model,
165
165
and brand/model may be undefined depending on the rule and implementation.
166
166
167
-
In case that no matching regex is found the value for family shall be "Other". Brand and model shall not be defined.
168
-
Leading and tailing whitespaces shall be trimmed from the result.
167
+
In case no matching regex is found, the value for family shall be "Other". Brand and model shall not be defined.
168
+
Leading and trailing whitespaces shall be trimmed from the result.
0 commit comments