Update docs/build/advanced-concepts/metadata-views.md

Co-authored-by: Greg Santos <gregsantos@gmail.com>

docs/build/advanced-concepts/metadata-views.md

@@ -22,7 +22,7 @@ In the context of Flow and its treatment of metadata for NFTs, there are two ess
 
 1. **`ViewResolver` for Contract-Level Metadata**:
     - This interface ensures that contracts, primarily those encapsulating NFT collections, adhere to the metadata views' standards.
-    - By adopting this interface, contracts can provide dynamic metadata outputs that encapsulate the collection as a whole.
+    - Through the adoption of this interface, contracts can provide dynamic metadata that represents the entirety of the collection.
 2. **`MetadataViews.Resolver` for NFT-Level Metadata**:
     - Used within individual NFT resources, this interface ensures each token adheres to a standardized metadata format.
     - It focuses on the unique aspects of an individual NFT, such as its unique ID, name, description, and other defining characteristics.