Skip to content

Commit 0032dd0

Browse files
committed
Fix typos.
1 parent d75e08d commit 0032dd0

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

CHANGELOG.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -50,9 +50,9 @@ Forge ChangeLog
5050

5151
## 1.3.1 - 2022-03-29
5252

53-
### Fixes
53+
### Fixed
5454
- RFC 3447 and RFC 8017 allow for optional `DigestAlgorithm` `NULL` parameters
55-
for `sha*` algorithms and require `NULL` paramters for `md2` and `md5`
55+
for `sha*` algorithms and require `NULL` parameters for `md2` and `md5`
5656
algorithms.
5757

5858
## 1.3.0 - 2022-03-17
@@ -164,11 +164,11 @@ Forge ChangeLog
164164
and is being removed rather than fixed.
165165
- **SECURITY**, **BREAKING**: Remove `forge.util.parseUrl()` (and
166166
`forge.http.parseUrl` alias) and use the [WHATWG URL
167-
Standard](https://url.spec.whatwg.org/). `URL` is supported by modern browers
168-
and modern Node.js. This change is needed to address URL parsing security
169-
issues. If `forge.util.parseUrl()` is used directly or through `forge.xhr` or
170-
`forge.http` APIs, and support is needed for environments without `URL`
171-
support, then a polyfill must be used.
167+
Standard](https://url.spec.whatwg.org/). `URL` is supported by modern
168+
browsers and modern Node.js. This change is needed to address URL parsing
169+
security issues. If `forge.util.parseUrl()` is used directly or through
170+
`forge.xhr` or `forge.http` APIs, and support is needed for environments
171+
without `URL` support, then a polyfill must be used.
172172
- **BREAKING**: Remove `forge.task` API. This API was never used, documented,
173173
or advertised by the maintainers. If anyone was using this API and wishes to
174174
continue development it in other project, please let the maintainers know.

0 commit comments

Comments
 (0)