Address review comments

Author: xing-yang

tags/tag-infrastructure/initiatives/storage-landscape/v3/topics/storage-attributes.md

@@ -36,7 +36,7 @@ Performance of a storage system is typically measured in terms of one or more of
 - Average and worst-case latency to perform storage operations to files, disk blocks or objects.
 - the number of storage operations that are possible per second
 - the throughput of data that can be stored or retrieved per second
-- The steady state and burst performance of the metrics above and other storage metrics.
+- The steady state and burst performance of the metrics above.
 
 Storage performance varies greatly from the combination of workloads, storage software layers, topology, and storage systems. Benchmarks and datasheets offer some guidance but experiments with real datasets and data processing unique to a workload produces a better prediction of deployed performance.
 
@@ -72,6 +72,8 @@ In modern computing environments, elasticity is a critical aspect of infrastruct
 
 In data management, elasticity means having the ability to optimize storage space usage by reclaiming storage when no longer needed. This can involve moving older data to less expensive storage tiers or archiving it to long-term storage to free up space for more critical data. Cloud infrastructure, which charges for every resource used, can benefit greatly from this feature, as it helps to prevent unnecessary costs from running services that are no longer required. An elastic infrastructure that can rapidly respond to changes in demand and adjust resource allocation accordingly is a vital component of modern IT systems, enabling organizations to maintain optimal performance, scalability, and cost-effectiveness.
 
+*The Observability and Elasticity attributes above are adapted from the [Data on Kubernetes Whitepaper - Database Patterns](https://github.com/cncf/tag-storage/blob/master/data-on-kubernetes-whitepaper/data-on-kubernetes-whitepaper-databases.md).*
+
 ## 3.8 Instantiation & Deployment
 
 A storage system can be deployed or instantiated on-premises or in a cloud environment in a variety of ways which defines where the storage solution or service can be deployed and/or consumed:

tags/tag-infrastructure/initiatives/storage-landscape/v3/topics/storage-stack-layers.md

@@ -133,6 +133,8 @@ Encryption services can be implemented for data in transit (protecting data in t
 
 The encryption function will often depend on integration with a key management system which may add complexity to a storage system.
 
+Encryption is only one part of a broader security posture. For a more detailed treatment of security topics such as transport layer security and certificate management, encryption at rest, and authentication/authorization integration with Kubernetes, see the [Security section](https://github.com/cncf/tag-storage/blob/master/data-on-kubernetes-whitepaper/data-on-kubernetes-whitepaper-databases.md#security) of the Data on Kubernetes Whitepaper - Database Patterns.
+
 ## 4.6 Physical / Non-Volatile Layer – terminology
 
 Storage systems will ultimately persist data on some form of physical storage layer which is generally non-volatile. The choice of the physical layer impacts the overall performance of the storage system and defines the long term durability of the stored dataset.