From 5703c9f388010ae08dd554d1104e55506eba0787 Mon Sep 17 00:00:00 2001
From: Philippe Proulx <eeppeliteloop@gmail.com>
Date: Fri, 4 Sep 2015 11:44:06 -0400
Subject: [PATCH] <div class="img"> -> <figure>

Signed-off-by: Philippe Proulx <eeppeliteloop@gmail.com>
---
 .../getting-started/tracing-your-own-user-application.md  | 4 ++--
 .../understanding-lttng/core-concepts/tracing-session.md  | 8 ++++----
 contents/understanding-lttng/plumbing/lttng-relayd.md     | 4 ++--
 contents/understanding-lttng/plumbing/overview.md         | 4 ++--
 contents/using-lttng/controlling-tracing/lttng-live.md    | 4 ++--
 5 files changed, 12 insertions(+), 12 deletions(-)

diff --git a/contents/getting-started/tracing-your-own-user-application.md b/contents/getting-started/tracing-your-own-user-application.md
index 5a8c130..95d2f37 100644
--- a/contents/getting-started/tracing-your-own-user-application.md
+++ b/contents/getting-started/tracing-your-own-user-application.md
@@ -152,9 +152,9 @@ gcc -o hello hello.o hello-tp.o -llttng-ust -ldl</strong>
 
 Here's the whole build process:
 
-<div class="img img-100">
+<figure class="img img-100">
 <img src="/images/docs26/ust-flow.png" alt="User space tracing's build process">
-</div>
+</figure>
 
 If you followed the
 [Tracing the Linux kernel](#doc-tracing-the-linux-kernel) tutorial, the
diff --git a/contents/understanding-lttng/core-concepts/tracing-session.md b/contents/understanding-lttng/core-concepts/tracing-session.md
index 96c0071..660a486 100644
--- a/contents/understanding-lttng/core-concepts/tracing-session.md
+++ b/contents/understanding-lttng/core-concepts/tracing-session.md
@@ -39,18 +39,18 @@ is a per-tracing session attribute, so that you may trace your target
 system/application in a given tracing session with a specific
 configuration while another one stays inactive.
 
-<div class="img img-100">
+<figure class="img img-100">
 <img src="/images/docs26/concepts.png" alt="LTTng concepts">
-</div>
+</figure>
 
 Conceptually, a tracing session is a per-user object; the
 [Plumbing](#doc-plumbing) section shows how this is actually
 implemented. Any user may create as many concurrent tracing sessions
 as desired.
 
-<div class="img img-100">
+<figure class="img img-100">
 <img src="/images/docs26/many-sessions.png" alt="Tracing sessions per user">
-</div>
+</figure>
 
 The trace data generated in a tracing session may be either saved
 to disk, sent over the network or not saved at all (in which case
diff --git a/contents/understanding-lttng/plumbing/lttng-relayd.md b/contents/understanding-lttng/plumbing/lttng-relayd.md
index a9590bd..5cb955c 100644
--- a/contents/understanding-lttng/plumbing/lttng-relayd.md
+++ b/contents/understanding-lttng/plumbing/lttng-relayd.md
@@ -30,9 +30,9 @@ _LTTng live_. LTTng live is an application protocol to view events as
 they arrive. The relay daemon still records events in trace files,
 but a _tee_ allows to inspect incoming events.
 
-<div class="img img-100">
+<figure class="img img-100">
 <img src="/images/docs26/lttng-live.png" alt="LTTng live">
-</div>
+</figure>
 
 Using LTTng live
 locally thus requires to run a local relay daemon.
diff --git a/contents/understanding-lttng/plumbing/overview.md b/contents/understanding-lttng/plumbing/overview.md
index 1d59454..36bdf7d 100644
--- a/contents/understanding-lttng/plumbing/overview.md
+++ b/contents/understanding-lttng/plumbing/overview.md
@@ -36,8 +36,8 @@ red arrows indicate control communications. The LTTng relay daemon is
 shown running on a remote system, although it could as well run on the
 target (monitored) system.
 
-<div class="img img-100">
+<figure class="img img-100">
 <img src="/images/docs26/plumbing-26.png" alt="LTTng plumbing">
-</div>
+</figure>
 
 Each component is described in the following subsections.
diff --git a/contents/using-lttng/controlling-tracing/lttng-live.md b/contents/using-lttng/controlling-tracing/lttng-live.md
index 657fde4..5307aae 100644
--- a/contents/using-lttng/controlling-tracing/lttng-live.md
+++ b/contents/using-lttng/controlling-tracing/lttng-live.md
@@ -17,9 +17,9 @@ As trace data is sent over the network to a relay daemon by a (possibly
 remote) consumer daemon, a _tee_ is created: trace data is recorded to
 trace files _as well as_ being transmitted to a connected live viewer:
 
-<div class="img img-100">
+<figure class="img img-100">
 <img src="/images/docs26/lttng-live.png" alt="LTTng live">
-</div>
+</figure>
 
 In order to use this feature, a tracing session must created in live
 mode on the target system:
-- 
2.34.1