From 764d07838c7bc945b716dc856ecb8f4a25f1cb3f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Daniel=20P=2E=20Berrang=C3=A9?= <berrange@redhat.com>
Date: Wed, 17 Jun 2020 12:21:58 +0100
Subject: [PATCH] docs: remove use of the term 'slave' in Jenkins agent docs
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Jenkins replaced use of the term 'slave' with 'agent' when
describing its architecture.

Reviewed-by: Peter Krempa <pkrempa@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
---
 docs/apps.html.in | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/apps.html.in b/docs/apps.html.in
index c24717faa2..c6d9a24fa7 100644
--- a/docs/apps.html.in
+++ b/docs/apps.html.in
@@ -141,9 +141,9 @@
       <dt><a href="https://plugins.jenkins.io/libvirt-slave/">Jenkins</a></dt>
       <dd>
         This plugin for Jenkins adds a way to control guest domains hosted
-        on Xen or QEMU/KVM.  You configure a Jenkins Slave,
+        on Xen or QEMU/KVM.  You configure a Jenkins Agent,
         selecting the guest domain and hypervisor.  When you need to build a
-        job on a specific Slave, its guest domain is started, then the job is
+        job on a specific Agent, its guest domain is started, then the job is
         run.  When the build process is finished, the guest domain is shut
         down, ready to be used again as required.
       </dd>