diff --git a/website/docs/using_rf_in_ci_systems/ci/jenkins.md b/website/docs/using_rf_in_ci_systems/ci/jenkins.md
index 28d63fb4..86e5c587 100644
--- a/website/docs/using_rf_in_ci_systems/ci/jenkins.md
+++ b/website/docs/using_rf_in_ci_systems/ci/jenkins.md
@@ -125,6 +125,7 @@ This is related especially to the use of Browser library which requires installa
 
 These are steps that needs to be done by the person administrating the Jenkins agents.
 - Install all the tools that are needed for running the tests: nodejs, python 3.x, Robot Framework, Browser library
+- Set ```PLAYWRIGHT_BROWSERS_PATH``` to point where you want to install browsers
 - Execute ```rfbrowser init``` to get the base setup for Browser library. Note that you still need to execute it with Jenkins user as well, see below.
 
 ### Preparing the Jenkins configuration file
@@ -133,6 +134,6 @@ These are steps you need to have in your Jenkins configuration. I recommend putt
 - ```npm config set registry https://local-site-for-node-modules``` <-- here you need a server that is providing all required node modules; if it doesn't exist proxy config might work as well
 - Additional commands that might be needed could be ```npm config set strict-ssl false``` or ```npm config set always-auth true```depending how the server is configured
 - Then run ```rfbrowser init --skip-browsers``` to avoid the installation of browsers that may appear hard over the firewall
-- ... and use instead the ones installed by root when the agent was initialised: ```export PLAYWRIGHT_BROWSERS_PATH=/home/jenkins/.cache/ms-playwright````
+- ... and use instead the ones installed by root when the agent was initialised by pointing with ```PLAYWRIGHT_BROWSERS_PATH```` to the location defined
 
 Now you should be ready to execute tests.