diff --git a/content/git/using-lfs.md b/content/git/using-lfs.md
index f3368e1..4984fb6 100644
--- a/content/git/using-lfs.md
+++ b/content/git/using-lfs.md
@@ -89,9 +89,9 @@ However, that should not be a problem as the files configured to be tracked by l
 You can reduce the size of the local repository (aka the `.git` folder) by calling `git lfs prune`.
 This will remove all files that are not in the current HEAD.
 
-**Caveat**: This means that older versions of the files are no longer stored on your local disk.
-If you check out an older commit that still references the file, it will be downloaded from the lfs server.
-If the server side is not available the requested version of the file will be inaccessible.
+> **Caveat**: This means that older versions of the files are no longer stored on your local disk.
+> If you check out an older commit that still references the file, it will be downloaded from the lfs server.
+> If the server side is not available the requested version of the file will be inaccessible.
 
 ## Enabling and Disabling LFS
 
@@ -99,9 +99,9 @@ Use [git lfs migrate][git-lfs-migrate] to enable or disable the tracking of file
 All changes done by lfs-migrate are done in your local working copy.
 Nothing will be done on the server side unless you push your changes to the server.
 
-**Note**: `git lfs migrate` will rewrite the history of your repository.
-So be sure that no one else is working with the repository during your changes.
-Also keep in mind, that all users must refresh their local repositories prior to doing changes to the altered repository.
+> **Note**: `git lfs migrate` will rewrite the history of your repository.
+> So be sure that no one else is working with the repository during your changes.
+> Also keep in mind, that all users must refresh their local repositories prior to doing changes to the altered repository.
 
 ### Enabling LFS in an existing repository