fix: some display

ninja_crud/testing/core/components/headers.py

@@ -8,8 +8,8 @@ class Headers:
     Manages HTTP request headers for various test scenarios.
 
     The Headers class is designed to simplify the process of defining and using different sets of
-    headers for multiple test scenarios. It supports defining headers for successful requests ('ok'),
-    as well as headers expected to result in forbidden ('forbidden') or unauthorized ('unauthorized')
+    headers for multiple test scenarios. It supports defining headers for successful requests (`ok`),
+    as well as headers expected to result in forbidden (`forbidden`) or unauthorized (`unauthorized`)
     responses.
 
     One of the key features is its ability to accept either a single dictionary (for testing a single
@@ -47,7 +47,7 @@ def __init__(
             forbidden (Union[dict, List[dict], None], optional): Headers expected to yield a 'forbidden'
                 response. Accepts a single dictionary or a list of dictionaries. Defaults to None.
             unauthorized (Union[dict, List[dict], None], optional): Headers expected to yield an 'unauthorized'
-                response. Like 'ok' and 'forbidden', it accepts both a single dictionary or a list. Defaults to None.
+                response. Like `ok` and `forbidden`, it accepts both a single dictionary or a list. Defaults to None.
         """
         self.ok: List[dict] = utils.ensure_list_of_dicts(ok)
         self.forbidden: Optional[List[dict]] = (

ninja_crud/testing/core/components/path_parameters.py

@@ -9,7 +9,7 @@ class PathParameters:
 
     The PathParameters class is designed to simplify the process of defining and using different sets of
     path parameters for multiple test scenarios. It supports defining path parameters for successful
-    requests ('ok'), as well as path parameters expected to result in not found ('not_found') responses.
+    requests (`ok`), as well as path parameters expected to result in not found (`not_found`) responses.
 
     One of the key features is its ability to accept either a single dictionary (for testing a single
     case) or a list of dictionaries (for testing multiple cases), providing a convenient way to test

ninja_crud/testing/core/components/payloads.py

@@ -8,8 +8,8 @@ class Payloads:
     Manages HTTP request payloads for various test scenarios.
 
     The Payloads class is designed to simplify the process of defining and using different sets of
-    payloads for multiple test scenarios. It supports defining payloads for successful requests ('ok'),
-    as well as payloads expected to result in bad request ('bad_request') or conflict ('conflict')
+    payloads for multiple test scenarios. It supports defining payloads for successful requests (`ok`),
+    as well as payloads expected to result in bad request (`bad_request`) or conflict (`conflict`)
     responses.
 
     One of the key features is its ability to accept either a single dictionary (for testing a single
@@ -46,7 +46,7 @@ def __init__(
             bad_request (Union[dict, List[dict], None], optional): Payloads expected to yield a 'bad request'
                 response. Accepts a single dictionary or a list of dictionaries. Defaults to None.
             conflict (Union[dict, List[dict], None], optional): Payloads expected to yield a 'conflict'
-                response. Like 'ok' and 'bad_request', it accepts both a single dictionary or a list. Defaults to None.
+                response. Like `ok` and `bad_request`, it accepts both a single dictionary or a list. Defaults to None.
         """
         self.ok: List[dict] = utils.ensure_list_of_dicts(ok)
         self.bad_request: Optional[List[dict]] = (

ninja_crud/testing/core/components/query_parameters.py

@@ -9,7 +9,7 @@ class QueryParameters:
 
     The QueryParameters class is designed to simplify the process of defining and using different sets of
     query parameters for multiple test scenarios. It supports defining query parameters for successful
-    requests ('ok'), as well as query parameters expected to result in bad request ('bad_request')
+    requests (`ok`), as well as query parameters expected to result in bad request (`bad_request`)
     responses.
 
     One of the key features is its ability to accept either a single dictionary (for testing a single