Restyled by prettier (#1513)

Co-authored-by: Restyled.io <[email protected]>

content/blog/2020-06-29-june-20-community-gems.md

@@ -41,11 +41,11 @@ _Just like this but with technical documentation._
 ### Q: After I pushed my local data to remote storage, I noticed the file names are different in my storage repository- they're hash values. [Can I make them more meaningful names?](https://discord.com/channels/485586884165107732/563406153334128681/717737163122540585)
 
 No, but for a good reason! What you're seeing are cached files, and they're
-stored with a special naming convention that makes DVC versioning and addressing possible-
-these file names are how DVC deduplicates data (to avoid keeping multiple copies
-of the same file version) and ensures that each unique version of a file is
-immutable. If you manually overwrote those filenames you would risk breaking Git
-version control. You can
+stored with a special naming convention that makes DVC versioning and addressing
+possible- these file names are how DVC deduplicates data (to avoid keeping
+multiple copies of the same file version) and ensures that each unique version
+of a file is immutable. If you manually overwrote those filenames you would risk
+breaking Git version control. You can
 [read more about how DVC uses this file format in our docs](https://dvc.org/doc/user-guide/dvc-files-and-directories#structure-of-cache-directory).
 
 It sounds like you're looking for ways to interact with DVC-tracked objects at a