Use italics instead of code formatting

pull/977/head
Will 4 years ago
parent ea9fced092
commit 68370677ef
No known key found for this signature in database
GPG Key ID: 385872BB265E8BF8

@ -457,8 +457,8 @@ that a particular MSC works) do not have to follow this process.
{{% boxes/note %}} {{% boxes/note %}}
MSCs MUST still describe what the stable endpoints/feature looks like MSCs MUST still describe what the stable endpoints/feature looks like
with a note towards the bottom for what the unstable feature with a note towards the bottom for what the unstable feature
flag/prefixes are. For example, an MSC would propose */_matrix/client/r0/new/endpoint*, not */_matrix/client/unstable/ flag/prefixes are. For example, an MSC would propose `/_matrix/client/r0/new/endpoint`, not `/_matrix/client/unstable/
com.example/new/endpoint*. com.example/new/endpoint`.
{{% /boxes/note %}} {{% /boxes/note %}}
In summary: In summary:
@ -473,7 +473,7 @@ In summary:
incurring by moving faster than the spec. incurring by moving faster than the spec.
- The vendor prefix is chosen by the developer of the feature, using - The vendor prefix is chosen by the developer of the feature, using
the Java package naming convention. The foundation's preferred the Java package naming convention. The foundation's preferred
vendor prefix is *org.matrix*. vendor prefix is `org.matrix`.
- The vendor prefixes, unstable feature flags, and unstable endpoints - The vendor prefixes, unstable feature flags, and unstable endpoints
should be included in the MSC, though the MSC MUST be written in a should be included in the MSC, though the MSC MUST be written in a
way that proposes new stable endpoints. Typically this is solved by way that proposes new stable endpoints. Typically this is solved by

Loading…
Cancel
Save