Remove incorrect comments about Badger2

config/profile.go

@@ -175,10 +175,6 @@ Use this datastore if some aspects of performance,
 especially the speed of adding many gigabytes of files, are critical.
 However, be aware that:
 
-* This datastore will not properly reclaim space when your datastore is
-  smaller than several gigabytes.  If you run IPFS with --enable-gc, you plan
-  on storing very little data in your IPFS node, and disk usage is more
-  critical than performance, consider using flatfs.
 * This datastore uses up to several gigabytes of memory.
 
 This profile may only be applied when first initializing the node.`,

docs/config.md

@@ -231,7 +231,7 @@ documented in `ipfs config profile --help`.
     enabled block-level garbage collection), you plan on storing very little data in
     your IPFS node, and disk usage is more critical than performance, consider using
     flatfs.
-  - This datastore uses up to several gigabytes of memory. 
+  - This datastore uses up to several gigabytes of memory.
 
   This profile may only be applied when first initializing the node.
 
@@ -245,13 +245,7 @@ documented in `ipfs config profile --help`.
   Use this datastore if some aspects of performance, 
   especially the speed of adding many gigabytes of files, are critical. However, be aware that:
 
-  - This datastore will not properly reclaim space when your datastore is
-    smaller than several gigabytes. If you run IPFS with `--enable-gc`, you plan on storing very little data in
-    your IPFS node, and disk usage is more critical than performance, consider using
-    `flatfs`.
   - This datastore uses up to several gigabytes of memory.  
-  - Good for medium-size datastores, but may run into performance issues if your dataset is bigger than a terabyte.
-  - The current implementation is based on old badger 1.x which is no longer supported by the upstream team.
 
   This profile may only be applied when first initializing the node.