fixes based on feedback from the product team

Author: jimmart-dev

articles/storage/blobs/blobfuse2-how-to-deploy.md

@@ -6,7 +6,7 @@ author: jammart
 ms.service: storage
 ms.subservice: blobs
 ms.topic: how-to
-ms.date: 09/29/2022
+ms.date: 10/01/2022
 ms.author: jammart
 ms.reviewer: tamram
 ---
@@ -52,7 +52,7 @@ lsb_release -a
 
 If there are no binaries available for your distribution, you can [build the binaries from source code](https://github.com/MicrosoftDocs/azure-docs-pr/pull/203174#option-2-build-from-source).
 
-#### Install the BlobFuse2 binaries
+#### Install the BlobFuse2 binariesFstream
 
 To install BlobFuse2:
 
@@ -134,15 +134,15 @@ BlobFuse2 provides native-like performance by using local file-caching technique
 
 #### Configure caching for streaming large files
 
-BlobFuse2 supports read- and write-streaming as an alternative to disk caching for large files. In streaming mode, BlobFuse2 caches blocks of large files in memory for both reading and writing. The configuration settings related to caching for streaming are under the `stream:` settings in your configuration file as follows:
+BlobFuse2 supports read- and write-streaming as an alternative to disk caching for files. In streaming mode, BlobFuse2 caches blocks of large files in memory for both reading and writing. The configuration settings related to caching for streaming are under the `stream:` settings in your configuration file as follows:
 
 ```yml
 stream:
-    Block-size-mb:
+    block-size-mb:
         For read only mode, the size of each block to be cached in memory while streaming (in MB)
         For read/write mode: the size of newly created blocks
-    Max-buffers: The total number of buffers to store blocks in
-    Buffer-size-mb: The size for each buffer
+    max-buffers: The total number of buffers to store blocks in
+    buffer-size-mb: The size for each buffer
 ```
 
 See [the sample streaming configuration file](https://github.com/Azure/azure-storage-fuse/blob/main/sampleStreamingConfig.yaml) to get started quickly with some settings for a basic streaming scenario.

articles/storage/blobs/blobfuse2-what-is.md

@@ -6,7 +6,7 @@ author: jammart
 ms.service: storage
 ms.subservice: blobs
 ms.topic: how-to
-ms.date: 09/29/2022
+ms.date: 10/01/2022
 ms.author: jammart
 ms.reviewer: tamram
 ---
@@ -124,7 +124,7 @@ However, there are some key differences in the way BlobFuse2 behaves:
 
 ### Data integrity
 
-The file caching behavior plays an important role in the integrity of the data being read and written to a Blob Storage file system mount. Streaming mode is recommended for use with large files, which supports both read- and write-streaming. BlobFuse2 caches blocks of streaming files in memory. For smaller files, the entire file is cached to a local disk.
+The file caching behavior plays an important role in the integrity of the data being read and written to a Blob Storage file system mount. Streaming mode is recommended for use with large files, which supports both read- and write-streaming. BlobFuse2 caches blocks of streaming files in memory. For smaller files that do not consist of blocks, the entire file is stored in memory. File cache is the second mode and is recommended for workloads that do not contain large files. Where files are stored on disk in their entirety.
 
 BlobFuse2 supports both read and write operations. Continuous synchronization of data written to storage by using other APIs or other mounts of BlobFuse2 isn't guaranteed. For data integrity, it's recommended that multiple sources don't modify the same blob, especially at the same time. If one or more applications attempt to write to the same file simultaneously, the results could be unexpected. Depending on the timing of multiple write operations and the freshness of the cache for each, the result could be that the last writer wins and previous writes are lost, or generally that the updated file isn't in the desired state.
 
@@ -134,7 +134,7 @@ When a file is written to, the data is first persisted into cache on a local dis
 
 #### Streaming
 
-For both read- and write-streaming, blocks of data are cached in memory as they are read or updated. Updates are flushed to Azure Storage when a file is closed.
+For both read- and write-streaming, blocks of data are cached in memory as they are read or updated. Updates are flushed to Azure Storage when a file is closed or when the buffer is filled with dirty blocks.
 
 Reading the same blob from multiple simultaneous threads is supported. However, simultaneous write operations could result in unexpected file data outcomes, including data loss. Performing simultaneous read operations and a single write operation is supported, but the data being read from some threads might not be current.