From 074040a1255e29b296c8f2710c9d554b2244e825 Mon Sep 17 00:00:00 2001
From: phillipwells <pwells@gitlab.com>
Date: Wed, 12 Mar 2025 11:23:31 -0500
Subject: [PATCH] Fix broken bulleted lists
---
.../dast/browser/configuration/customize_settings.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/user/application_security/dast/browser/configuration/customize_settings.md b/doc/user/application_security/dast/browser/configuration/customize_settings.md
index 21fc39eaa2b0..2ab2920e8f85 100644
--- a/doc/user/application_security/dast/browser/configuration/customize_settings.md
+++ b/doc/user/application_security/dast/browser/configuration/customize_settings.md
@@ -181,7 +181,7 @@ each step in the process:
1. Parse content and renders the initial page.
1. Trigger the standard "document ready" event.
- This phase uses either `DAST_PAGE_READY_AFTER_NAVIGATION_TIMEOUT` (for full page loads) or `DAST_PAGE_READY_AFTER_ACTION_TIMEOUT` (for in-page actions), which sets the maximum wait time for document loading.
+ This phase uses either `DAST_PAGE_READY_AFTER_NAVIGATION_TIMEOUT` (for full page loads) or `DAST_PAGE_READY_AFTER_ACTION_TIMEOUT` (for in-page actions), which sets the maximum wait time for document loading.
1. **Client-Side rendering**: After initial loading, many single-page applications:
@@ -190,7 +190,7 @@ each step in the process:
- Render a DOM and performs updates based on fetched data (`DAST_PAGE_DOM_READY_TIMEOUT`).
- Display page loading indicators (`DAST_PAGE_IS_LOADING_ELEMENT`).
- The scanner monitors these activities to determine when the page is ready for interaction.
+ The scanner monitors these activities to determine when the page is ready for interaction.
The following chart illustrates the sequence timeouts used when crawling a page:
--
GitLab