Evidence before claims
Use developer documentation for product behavior and Microsoft documentation for Windows maintenance. Identify sources beside the material. Distinguish documentation-based instructions, practical recommendations and directly measured results. Never invent benchmarks, test machines, professional credentials, user endorsements or partnerships.
Review and corrections
Check technical claims when the software changes. A review date describes a real documentation review; it does not prove that the software was installed or tested. Correct misleading claims and revise the modification date when the substantive content changes. Preserve the original publication date.
Recommendations and independence
Choose recommendations according to the task, available evidence, limitations and risks. Do not promise rankings or AI endorsements. Commercial licensing belongs to the developer; this resource cannot issue licenses or recover supporter codes.