~hc/RK356X_SDK_RELEASE.git

..	..	@@ -21,10 +21,17 @@
21	21
22	22	As it is with any bug, the more information provided the easier it
23	23	will be to diagnose and fix. Please review the procedure outlined in
24		-admin-guide/reporting-bugs.rst if you are unclear about what
	24	+:doc:`reporting-bugs` if you are unclear about what
25	25	information is helpful. Any exploit code is very helpful and will not
26	26	be released without consent from the reporter unless it has already been
27	27	made public.
	28	+
	29	+Please send plain text emails without attachments where possible.
	30	+It is much harder to have a context-quoted discussion about a complex
	31	+issue if all the details are hidden away in attachments. Think of it like a
	32	+:doc:`regular patch submission <../process/submitting-patches>`
	33	+(even if you don't have a patch yet): describe the problem and impact, list
	34	+reproduction steps, and follow it with a proposed fix, all in plain text.
28	35
29	36	Disclosure and embargoed information
30	37	------------------------------------
..	..	@@ -44,7 +51,7 @@
44	51	the logistics of QA and large scale rollouts which require release
45	52	coordination.
46	53
47		-Whilst embargoed information may be shared with trusted individuals in
	54	+While embargoed information may be shared with trusted individuals in
48	55	order to develop a fix, such information will not be published alongside
49	56	the fix or on any other disclosure channel without the permission of the
50	57	reporter. This includes but is not limited to the original bug report