From aa5fcc94f644d0de7e7d3a6071e3080f84d63603 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andr=C3=A9s=20Suero?=
 <40367219+andressuy@users.noreply.github.com>
Date: Fri, 6 Dec 2019 17:08:38 -0300
Subject: [PATCH] Updated to rTorrent 0.9 settings (missed one)

---
 RPC-Setup-XMLRPC.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/RPC-Setup-XMLRPC.md b/RPC-Setup-XMLRPC.md
index a9129be..5ed47d2 100644
--- a/RPC-Setup-XMLRPC.md
+++ b/RPC-Setup-XMLRPC.md
@@ -117,7 +117,7 @@ The web server will now route xmlrpc requests to rtorrent, which is listening on
 
 :bangbang: **Never** bind the SCGI port to anything *but* 127.0.0.1. Anyone who can send rtorrent xmlrpc commands does have the ability to execute code with the privileges of the user running rtorrent. If you want to be more secure on principle, use UNIX domain sockets instead of TCP ports (see below).
 
-You may also use `scgi_local = /foo/bar` to create a local domain socket, which supports file permissions. Set the rw permissions of the directory the socket will reside in to only allow the necessary processes. This is the recommended way of using XMLRPC with rtorrent, though not all http servers support local domain sockets for scgi.
+You may also use `network.scgi.open_local = /foo/bar` to create a local domain socket, which supports file permissions. Set the rw permissions of the directory the socket will reside in to only allow the necessary processes. This is the recommended way of using XMLRPC with rtorrent, though not all http servers support local domain sockets for scgi.
 
 ## Test and usage