From 2039a7e7cea342df1016128a542070d87728e2e1 Mon Sep 17 00:00:00 2001
From: Fontrodona Nicolas <nicolas.fontrodona@ens-lyon.fr>
Date: Mon, 20 Feb 2023 09:55:12 +0100
Subject: [PATCH] README.qmd: update
---
README.qmd | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/README.qmd b/README.qmd
index b2007f0..2fa40b4 100644
--- a/README.qmd
+++ b/README.qmd
@@ -582,8 +582,8 @@ You may want to put those settings in a local or in a global configuration file
gblk provide a way to do that by using the borg configuration file `.borg/config` as a local configuration file and the `~/.gblkconfig` file as a global configuration file.
-::: {.callout-note}
-**If both the local and global configuration files contain gblk settings used for pruning, only the local settings are used..**
+::: {.callout-important}
+If both the local and global configuration files contain gblk settings used for pruning, only the local settings are used.
:::
### Add new settings in configuration file
@@ -659,8 +659,8 @@ Finnaly, to prune your results archives using the settings defined in the global
gblk config prune [OPTION]
```
-::: {.callout-note}
-**If both the local and global configuration files contain gblk settings used for pruning, only the local settings are used..**
+::: {.callout-important}
+If both the local and global configuration files contain gblk settings used for pruning, only the local settings are used.
:::
You can see what option you can add to your command with
--
GitLab