From a59e4a9b2dae3f1050ef4b6824cdb418ac051946 Mon Sep 17 00:00:00 2001 From: tonykelly-octopus <109653283+tonykelly-octopus@users.noreply.github.com> Date: Wed, 30 Oct 2024 04:47:56 +0000 Subject: [PATCH] Image border fix on DFS page --- src/pages/docs/installation/file-storage/local-storage.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/pages/docs/installation/file-storage/local-storage.mdx b/src/pages/docs/installation/file-storage/local-storage.mdx index 09c4c41610..f53891148f 100644 --- a/src/pages/docs/installation/file-storage/local-storage.mdx +++ b/src/pages/docs/installation/file-storage/local-storage.mdx @@ -77,4 +77,6 @@ Octopus does not need to be restarted in this scenario. Customers can either do In the simplified diagram below, when an outage at DFS Replica `\\SVR_ONE\Public` occurs, by re-configuring each Octopus node to use a different replica (ensuring all nodes are re-configured to the same replica), customers can still take advantage of the redundancy within DFS. -![Using DFS for redundancy with Octopus Deploy](/docs/getting-started/best-practices/images/dfs-for-redundancy.png) \ No newline at end of file +:::figure +![Using DFS for redundancy with Octopus Deploy](/docs/getting-started/best-practices/images/dfs-for-redundancy.png) +:::