From f3129c908cde70efeddf356dac4b3a2c33aa2c1f Mon Sep 17 00:00:00 2001
From: baldurk <baldurk@baldurk.org>
Date: Mon, 24 Feb 2025 17:18:43 +0000
Subject: [PATCH] Clarify renderdoc module vs library for python

---
 docs/python_api/dev_environment.rst          | 2 --
 docs/python_api/examples/renderdoc_intro.rst | 2 +-
 2 files changed, 1 insertion(+), 3 deletions(-)

diff --git a/docs/python_api/dev_environment.rst b/docs/python_api/dev_environment.rst
index f09111f71..0eddbb248 100644
--- a/docs/python_api/dev_environment.rst
+++ b/docs/python_api/dev_environment.rst
@@ -17,8 +17,6 @@ Build instructions for your platform are available `on github <https://github.co
   
   RenderDoc requires pythonXY.lib, include files such as include/Python.h, as well as a .zip of the standard library. If you installed python with an installer you have the first two, and can generate the standard library zip by zipping the contents of the Lib folder. If you downloaded the embeddable zip distribution you will only have the standard library zip, you need to obtain the include files and ``.lib`` file separately.
 
-Once you have compiled RenderDoc copy the python module into the same folder as the main renderdoc library. On windows this means copying out of the ``pymodules`` subdirectory, on linux this will likely be the case already. We do this to keep things simple, so the python module can load the library without needing to change ``PATH``.
-
 Python Setup for VS Code
 ------------------------
 Using the same python version as the RenderDoc build used (Python 3.6 by default).
diff --git a/docs/python_api/examples/renderdoc_intro.rst b/docs/python_api/examples/renderdoc_intro.rst
index 15e4dfd10..b606f63ad 100644
--- a/docs/python_api/examples/renderdoc_intro.rst
+++ b/docs/python_api/examples/renderdoc_intro.rst
@@ -31,7 +31,7 @@ Once you have the module, either place the module within your python's default l
 
     sys.path.append('/path/to/renderdoc/module')
 
-Additionally, the renderdoc python module needs to be able to load the main renderdoc library - the module library it self just contains stubs and python wrappers for the C++ interfaces. You can either place the renderdoc library in the system library paths, or solve it in a platform specific way. For example on windows you can either place ``renderdoc.dll`` in the same directory as the python module, or append to ``PATH``. On Python 3.8 and above ``PATH`` is no longer searched by default so you need to explicitly add the DLL folder:
+Additionally, the renderdoc python module needs to be able to load the main renderdoc library (``renderdoc.dll`` or ``librenderdoc.so`` depending on your platform) - the module library itself just contains stubs and python wrappers for the C++ interfaces. You can either place the renderdoc library in the system library paths, or solve it in a platform specific way. For example on windows you can either place ``renderdoc.dll`` in the same directory as the python module, or append to ``PATH``. On Python 3.8 and above ``PATH`` is no longer searched by default so you need to explicitly add the DLL folder:
 
 .. highlight:: python
 .. code:: python