fix inline emphasis

Author: masc2023

process/process_areas/problem_resolution/guidance/problem_resolution_guideline.rst

@@ -177,21 +177,21 @@ If applicable, the features affected should be identified too.
 
 The description shall reflect the result of the analysis.
 
-Topics to checked (critical topics are marked with *):
+Topics to checked (critical topics are marked with x):
 
-- [*] Is the problem description clear and detailed enough to understand the problem and its impact?
-- [*] Is the problem root cause clearly described?
-- [*] Is the problem impact clearly described?
+- [x] Is the problem description clear and detailed enough to understand the problem and its impact?
+- [x] Is the problem root cause clearly described?
+- [x] Is the problem impact clearly described?
 - [ ] Is notification of affected parties required? If yes, are the affected parties notified?
 - [ ] Are there any proposed solutions provided?
 - [ ] Are there any further linked issues or pull requests provided?
-- [*] Is the error occurrence rate provided? If yes, is it high enough to accept the problem?
-- [*] Is the problem reproducible?
+- [x] Is the error occurrence rate provided? If yes, is it high enough to accept the problem?
+- [x] Is the problem reproducible?
 - [ ] Are there any further supporting information provided?
-- [*] Is the problem classification correct?
-- [*] Is information for the affected version of the release provided? If yes, is it correct?
+- [x] Is the problem classification correct?
+- [x] Is information for the affected version of the release provided? If yes, is it correct?
 - [ ] Is the information for the expected closure version provided? If yes, is it correct?
-- [*] Is the problem affecting safety or security? If yes, is the classification correct?
+- [x] Is the problem affecting safety or security? If yes, is the classification correct?
 
 The analysis phase can not be closed, until all critical topics are
 clarified and provided in the description. If not, the problem report should be rejected