Fix grammatical errors after code review
This commit is contained in:
parent
c9a36e4340
commit
39d768af82
2 changed files with 2 additions and 2 deletions
|
|
@ -7,7 +7,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
|
|||
## Unreleased
|
||||
|
||||
### Added
|
||||
- We mark our MFM posts as FEP-c16b compliant, and do not re-parsed when receiving an MFM post who is marked as FEP-c16b compliant.
|
||||
- We mark our MFM posts as FEP-c16b compliant, and retain remote HTML representations for incoming posts marked as FEP-c16b-compliant. (Safety scrubbers are still applied)
|
||||
|
||||
## 2025.03
|
||||
|
||||
|
|
|
|||
|
|
@ -35,7 +35,7 @@ Depending on instance configuration the same may be true for GET requests.
|
|||
### FEP-c16b: Formatting MFM functions
|
||||
|
||||
We set the optional extension term `htmlMfm: true` when using content type "text/x.misskeymarkdown".
|
||||
Incomming messages containing `htmlMfm: true` will not have their content re-parsed.
|
||||
Incoming messages containing `htmlMfm: true` will not have their content re-parsed.
|
||||
|
||||
## Nodeinfo
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue