[deploy site] fixing bug 2402, detectify link removal (#2407) 0b29bc6

Author: selenium-ci

documentation/_print/index.html

@@ -149777,9 +149777,8 @@
 thay can vary between different environments. For example a <strong>Hub/Node</strong> with 120 <strong>Nodes</strong>
 might work well when the <strong>Hub</strong> has enough resources. Values below are not set on stone,
 and feedback is welcomed!</p><h3 id=small>Small</h3><p><strong>Standalone</strong> or <strong>Hub/Node</strong> with 5 or less <strong>Nodes</strong>.</p><h3 id=middle>Middle</h3><p><strong>Hub/Node</strong> between 6 and 60 <strong>Nodes</strong>.</p><h3 id=large>Large</h3><p><strong>Hub/Node</strong> between 60 and 100 <strong>Nodes</strong>. <strong>Distributed</strong> with over 100 <strong>Nodes</strong>.</p><h2 id=warning>Warning</h2><p>Selenium Grid must be protected from external access using appropriate
-firewall permissions.</p><p>Failure to protect your Grid could result in one or more of the following occurring:</p><ul><li>You provide open access to your Grid infrastructure</li><li>You allow third parties to access internal web applications and files</li><li>You allow third parties to run custom binaries</li></ul><p>See this blog post on <a href=/>Detectify</a>, which gives a good
-overview of how a publicly exposed Grid could be misused:
-<a href=//labs.detectify.com/2017/10/06/guest-blog-dont-leave-your-grid-wide-open/>Don&rsquo;t Leave your Grid Wide Open</a></p><h2 id=further-reading>Further reading</h2><ul><li><a href=https://www.selenium.dev/documentation/grid/components/>Components</a>: learn how Grid&rsquo;s internal components relate to each other.</li><li><a href=https://www.selenium.dev/documentation/grid/configuration/>Configuration</a>: customize your Grid setup.</li><li><a href=https://www.selenium.dev/documentation/grid/architecture/>Architecture</a>: understand key concepts in Grid.</li><li><a href=https://www.selenium.dev/documentation/grid/advanced_features/>Advanced Features</a>: explore more possibilities through Grid&rsquo;s features.</li></ul></div><div class=td-content style=page-break-before:always><h1 id=pg-0b04eda1b3eb8ca7f1a0da30d5475930>4.2 - When to Use Grid</h1><div class=lead>Is Grid right for you?</div><p>When would you use a Selenium Grid?</p><ul><li>To run your tests in parallel, against different browser types, browser versions, operating systems</li><li>To reduce the time needed to execute a test suite</li></ul><p>Selenium Grid runs test suites in parallel against multiple machines (called Nodes).
+firewall permissions.</p><p>Failure to protect your Grid could result in one or more of the following occurring:</p><ul><li>You provide open access to your Grid infrastructure</li><li>You allow third parties to access internal web applications and files</li><li>You allow third parties to run custom binaries</li></ul><p>See this blog post on Detectify Labs, which gives a good overview of how a publicly exposed Grid could be misused:
+<a href=//labs.detectify.com/2017/10/06/guest-blog-dont-leave-your-grid-wide-open/>Don&rsquo;t Leave your Grid Wide Open</a>.</p><h2 id=further-reading>Further reading</h2><ul><li><a href=https://www.selenium.dev/documentation/grid/components/>Components</a>: learn how Grid&rsquo;s internal components relate to each other.</li><li><a href=https://www.selenium.dev/documentation/grid/configuration/>Configuration</a>: customize your Grid setup.</li><li><a href=https://www.selenium.dev/documentation/grid/architecture/>Architecture</a>: understand key concepts in Grid.</li><li><a href=https://www.selenium.dev/documentation/grid/advanced_features/>Advanced Features</a>: explore more possibilities through Grid&rsquo;s features.</li></ul></div><div class=td-content style=page-break-before:always><h1 id=pg-0b04eda1b3eb8ca7f1a0da30d5475930>4.2 - When to Use Grid</h1><div class=lead>Is Grid right for you?</div><p>When would you use a Selenium Grid?</p><ul><li>To run your tests in parallel, against different browser types, browser versions, operating systems</li><li>To reduce the time needed to execute a test suite</li></ul><p>Selenium Grid runs test suites in parallel against multiple machines (called Nodes).
 For large and long-running test suites, this can save minutes, hours, or perhaps days.
 This shortens the turnaround time for test results as your application under test (AUT)
 changes.</p><p>Grid can run tests (in parallel) against multiple different browsers, and it can

documentation/grid/_print/index.html

@@ -91,9 +91,8 @@
 thay can vary between different environments. For example a <strong>Hub/Node</strong> with 120 <strong>Nodes</strong>
 might work well when the <strong>Hub</strong> has enough resources. Values below are not set on stone,
 and feedback is welcomed!</p><h3 id=small>Small</h3><p><strong>Standalone</strong> or <strong>Hub/Node</strong> with 5 or less <strong>Nodes</strong>.</p><h3 id=middle>Middle</h3><p><strong>Hub/Node</strong> between 6 and 60 <strong>Nodes</strong>.</p><h3 id=large>Large</h3><p><strong>Hub/Node</strong> between 60 and 100 <strong>Nodes</strong>. <strong>Distributed</strong> with over 100 <strong>Nodes</strong>.</p><h2 id=warning>Warning</h2><p>Selenium Grid must be protected from external access using appropriate
-firewall permissions.</p><p>Failure to protect your Grid could result in one or more of the following occurring:</p><ul><li>You provide open access to your Grid infrastructure</li><li>You allow third parties to access internal web applications and files</li><li>You allow third parties to run custom binaries</li></ul><p>See this blog post on <a href=/>Detectify</a>, which gives a good
-overview of how a publicly exposed Grid could be misused:
-<a href=//labs.detectify.com/2017/10/06/guest-blog-dont-leave-your-grid-wide-open/>Don&rsquo;t Leave your Grid Wide Open</a></p><h2 id=further-reading>Further reading</h2><ul><li><a href=https://www.selenium.dev/documentation/grid/components/>Components</a>: learn how Grid&rsquo;s internal components relate to each other.</li><li><a href=https://www.selenium.dev/documentation/grid/configuration/>Configuration</a>: customize your Grid setup.</li><li><a href=https://www.selenium.dev/documentation/grid/architecture/>Architecture</a>: understand key concepts in Grid.</li><li><a href=https://www.selenium.dev/documentation/grid/advanced_features/>Advanced Features</a>: explore more possibilities through Grid&rsquo;s features.</li></ul></div><div class=td-content style=page-break-before:always><h1 id=pg-0b04eda1b3eb8ca7f1a0da30d5475930>2 - When to Use Grid</h1><div class=lead>Is Grid right for you?</div><p>When would you use a Selenium Grid?</p><ul><li>To run your tests in parallel, against different browser types, browser versions, operating systems</li><li>To reduce the time needed to execute a test suite</li></ul><p>Selenium Grid runs test suites in parallel against multiple machines (called Nodes).
+firewall permissions.</p><p>Failure to protect your Grid could result in one or more of the following occurring:</p><ul><li>You provide open access to your Grid infrastructure</li><li>You allow third parties to access internal web applications and files</li><li>You allow third parties to run custom binaries</li></ul><p>See this blog post on Detectify Labs, which gives a good overview of how a publicly exposed Grid could be misused:
+<a href=//labs.detectify.com/2017/10/06/guest-blog-dont-leave-your-grid-wide-open/>Don&rsquo;t Leave your Grid Wide Open</a>.</p><h2 id=further-reading>Further reading</h2><ul><li><a href=https://www.selenium.dev/documentation/grid/components/>Components</a>: learn how Grid&rsquo;s internal components relate to each other.</li><li><a href=https://www.selenium.dev/documentation/grid/configuration/>Configuration</a>: customize your Grid setup.</li><li><a href=https://www.selenium.dev/documentation/grid/architecture/>Architecture</a>: understand key concepts in Grid.</li><li><a href=https://www.selenium.dev/documentation/grid/advanced_features/>Advanced Features</a>: explore more possibilities through Grid&rsquo;s features.</li></ul></div><div class=td-content style=page-break-before:always><h1 id=pg-0b04eda1b3eb8ca7f1a0da30d5475930>2 - When to Use Grid</h1><div class=lead>Is Grid right for you?</div><p>When would you use a Selenium Grid?</p><ul><li>To run your tests in parallel, against different browser types, browser versions, operating systems</li><li>To reduce the time needed to execute a test suite</li></ul><p>Selenium Grid runs test suites in parallel against multiple machines (called Nodes).
 For large and long-running test suites, this can save minutes, hours, or perhaps days.
 This shortens the turnaround time for test results as your application under test (AUT)
 changes.</p><p>Grid can run tests (in parallel) against multiple different browsers, and it can