From fda5f7cd5756fc4c6e43accf7aa24b0a2f78783c Mon Sep 17 00:00:00 2001
From: sjjh <2787214+sjjh@users.noreply.github.com>
Date: Wed, 18 Dec 2024 14:30:57 +0100
Subject: [PATCH] Update multiple-devices.md: typo (, -> /)

The explanation string of the opencl_device_priority parameter contained a "," where in my understanding it should be a "/".
---
 content/special-topics/opencl/multiple-devices.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/special-topics/opencl/multiple-devices.md b/content/special-topics/opencl/multiple-devices.md
index 8ca722678e..1610115629 100644
--- a/content/special-topics/opencl/multiple-devices.md
+++ b/content/special-topics/opencl/multiple-devices.md
@@ -14,7 +14,7 @@ The computational demand varies significantly depending on the type of pixelpipe
 
 The configuration parameter “opencl\_device\_priority” holds a string with the following structure:
 
-`a,b,c.../d,e,f.../g,h,i.../j,k,l...,m,n,o...`
+`a,b,c.../d,e,f.../g,h,i.../j,k,l.../m,n,o...`
 
 Each letter represents one specific OpenCL device. There are five fields in the parameter string separated by a slash, each representing one type of pixelpipe. `a,b,c...` defines the devices that are allowed to process the center image (full) pixelpipe. Likewise devices `d,e,f...` can process the preview pixelpipe, devices `g,h,i...` the export pixelpipes, devices `j,k,l...` the thumbnail pixelpipes and finally devices `m,n,o...` preview pixelpipe for the second window. An empty field means that no OpenCL device may serve this type of pixelpipe.