Clarify that changelog entries end with a full stop

6 years ago · 5f12419afb
parent fcc26d247e
commit 5f12419afb
2 changed files with 4 additions and 4 deletions
--- a/CONTRIBUTING.rst
+++ b/CONTRIBUTING.rst
@ -99,7 +99,7 @@ the ``newsfragments`` directory. The ``type`` can be one of the following:
 * ``deprecation`` - Used when deprecating something
 All news fragments must have a brief summary explaining the change in the contents
-of the file.
+of the file. The summary must end in a full stop to be in line with the style guide.
 Changes that do not change the spec, such as changes to the build script, formatting,
 CSS, etc should not get a news fragment.
--- a/changelogs/client_server/newsfragments/1744.clarification
+++ b/changelogs/client_server/newsfragments/1744.clarification
@ -1 +1 @@
-Add missing status_msg to m.presence schema
+Add missing status_msg to m.presence schema.
`@ -1 +1 @@`
	`Add missing status_msg to m.presence schema`	`Add missing status_msg to m.presence schema.`