X-Git-Url: https://gerrit.fd.io/r/gitweb?a=blobdiff_plain;ds=sidebyside;f=docs%2Fcontent%2Fmethodology%2Fdata_plane_throughput%2Fplrsearch.md;h=1facccc63b545d88c6be476f3289485fa93a051c;hb=e6655fbc1f65e2e4599afd43e52a8cbecb810fe9;hp=2933b09b6be36c3c520f42c5a206dbe528739ce5;hpb=90e7db16a6652847489be214372cadb2b882c61b;p=csit.git

diff --git a/docs/content/methodology/data_plane_throughput/plrsearch.md b/docs/content/methodology/data_plane_throughput/plrsearch.md
index 2933b09b6b..1facccc63b 100644
--- a/docs/content/methodology/data_plane_throughput/plrsearch.md
+++ b/docs/content/methodology/data_plane_throughput/plrsearch.md
@@ -1,5 +1,4 @@
 ---
-bookToc: false
 title: "PLRsearch"
 weight: 3
 ---
@@ -325,7 +324,7 @@ With that in mind, the apparent narrowness of the interval
 is not a sign of low quality, just a consequence of PLRsearch assuming
 the performance stays constant.
 
-{{< svg "static/PLR_patch.svg" >}}
+{{< figure src="/cdocs/PLR_patch.svg" >}}
 
 #### Vhost
 
@@ -343,7 +342,7 @@ In other words, human only seeing estimates from one fitting function
 would expect narrower end interval, but human seeing the measured loss ratios
 agrees that the interval should be wider than that.
 
-{{< svg "static/PLR_vhost.svg" >}}
+{{< figure src="/cdocs/PLR_vhost.svg" >}}
 
 #### Summary