edit pass: data-manager-for-agri-concepts

Author: ShawnJackson

articles/data-manager-for-agri/concepts-farm-operations-data.md

@@ -10,12 +10,12 @@ ms.custom: template-concept
 ---
 # Work with farm activities data in Azure Data Manager for Agriculture
 
-Data about farm activities is one of the most important ground-truth datasets in precision agriculture. These machine-generated reports preserve the record of what exactly happened and when. That record can help improve in-field practice and the downstream value-chain analytics.
+Data about farm activities is one of the most important ground-truth datasets in precision agriculture. These machine-generated reports preserve the record of exactly what happened and when. That record can help improve in-field practice and the downstream value-chain analytics.
 
 Azure Data Manager for Agriculture supports both:
 
-* Summary data: Entered as properties in the operation data item directly.
-* Precision data: Uploaded as an attachment file (for example, .shp, .dat, or .isoxml) and reference linked to the operation data item.
+* **Summary data**: Entered as properties directly in the operation data item.
+* **Precision data**: Uploaded as an attachment file (for example, .shp, .dat, or .isoxml) and reference linked to the operation data item.
 
 New operation data can be pushed into the service via the APIs for operation and attachment creation. Or, if the desired source is in the supported list of original equipment manufacturer (OEM) connectors, data can be synced automatically from providers like Climate FieldView with an ingestion job for farm operations.
 
@@ -25,7 +25,7 @@ Azure Data Manager for Agriculture supports a range of data about farm activitie
 
 ## Integration with manufacturers of farm equipment
 
-Azure Data Manager for Agriculture fetches the associated data about farm activities (planting, application, tillage, and harvest) from the data provider (for example, Climate FieldView) by creating a data ingestion job for farm activities. For more information, see [Working with Farm Activities and activity data in Azure Data Manager for Agriculture](./how-to-ingest-and-egress-farm-operations-data.md).
+Azure Data Manager for Agriculture fetches the associated data about farm activities (planting, application, tillage, and harvest) from the data provider (for example, Climate FieldView) by creating a data ingestion job for farm activities. For more information, see [Working with farm activities and activity data in Azure Data Manager for Agriculture](./how-to-ingest-and-egress-farm-operations-data.md).
 
 ## Next steps
 

articles/data-manager-for-agri/concepts-ingest-satellite-imagery.md

@@ -12,7 +12,7 @@ show_latex: true
 
 # Ingest satellite imagery in Azure Data Manager for Agriculture
 
-Satellite imagery is a foundational pillar of agriculture data. To support scalable ingestion of geometry-clipped imagery, we partnered with Sentinel Hub by Sinergise to provide a seamless bring your own license (BYOL) experience for Azure Data Manager for Agriculture. You can use this BYOL experience to manage your own costs. This capability helps you with storing your field-clipped historical and up-to-date imagery in the linked context of the relevant fields.
+Satellite imagery is a foundational pillar of agriculture data. To support scalable ingestion of geometry-clipped imagery, Microsoft partnered with Sentinel Hub by Sinergise to provide a seamless bring your own license (BYOL) experience for Azure Data Manager for Agriculture. You can use this BYOL experience to manage your own costs. This capability helps you with storing your field-clipped historical and up-to-date imagery in the linked context of the relevant fields.
 
 ## Prerequisites
 
@@ -34,7 +34,7 @@ Because all ingested data is under a BYOL model, the cost of a job is transparen
 
 ## STAC search for available imagery
 
-Azure Data Manager for Agriculture supports the industry-standard [SpatioTemporal Asset Catalogs (STAC)](https://stacspec.org/en) search interface to find metadata on imagery in the Sentinel Hub collection before committing to downloading pixels. To do so, the search endpoint accepts a location in the form of a point, polygon, or multipolygon, plus a start and end date/time. Alternatively, if you already have the unique item ID, you can provide it as an array of up to 5 to retrieve those specific items directly.
+Azure Data Manager for Agriculture supports the industry-standard [SpatioTemporal Asset Catalogs (STAC)](https://stacspec.org/en) search interface to find metadata on imagery in the Sentinel Hub collection before committing to downloading pixels. To do so, the search endpoint accepts a location in the form of a point, polygon, or multipolygon, plus a start and end date/time. Alternatively, if you already have the unique item ID, you can provide it as an array of up to five to retrieve those specific items directly.
 
 > [!IMPORTANT]
 > To be consistent with STAC syntax, *feature ID* is renamed to *item ID* from the 2023-11-01-preview API version.
@@ -55,7 +55,7 @@ In some cases, using more than one tile isn't desirable and traceability to a si
 ## Reprojection
 
 > [!IMPORTANT]
-> Reprojection functionality has changed from the 2023-11-01-preview API version, but it's immediately applicable to all versions. Older versions used a static conversion of 10m*10m set at the equator. Imagery ingested before this release might have a difference in size from imagery ingested after this release.
+> Reprojection functionality has changed from the 2023-11-01-preview API version, but it's immediately applicable to all versions. Older versions used a static conversion of 10 m * 10 m set at the equator. Imagery ingested before this release might have a difference in size from imagery ingested after this release.
 
 Azure Data Manager for Agriculture uses WGS84 (EPSG: 4326), a flat coordinate system. Sentinel-2 imagery is presented in UTM, a ground projection system that approximates the round earth.
 
@@ -80,17 +80,17 @@ $$
 > [!IMPORTANT]
 > Caching functionality is available only from the 2023-11-01-preview API version. Item caching is applicable only for retrieval that's based on item ID. For a typical geometry and time search, the returned items aren't cached.
 
-Azure Data Manager for Agriculture optimizes performance and costing of highly repeated calls to the same item. It caches recent STAC items when retrieved by item ID for five days in the customer's instance and enables local retrieval.
+Azure Data Manager for Agriculture optimizes performance and costing of highly repeated calls to the same item. It caches recent STAC items retrieved by item ID for five days in the customer's instance and enables local retrieval.
 
-For the first call to the search endpoint, Azure Data Manager for Agriculture brokers the request and triggers a request to the upstream provider to retrieve the matching or intersecting data items. It incurs any provider fees.
+For the first call to the search endpoint, Azure Data Manager for Agriculture brokers the request and triggers a request to the upstream provider to retrieve the matching or intersecting data items. The request incurs any provider fees.
 
 Any subsequent search first directs to the cache for a match. If there's a match, data is served from the cache directly. This process doesn't result in a call to the upstream provider, so it doesn't incur more provider fees. If there's no match, or if the five-day retention period elapses, a subsequent call for the data is passed to the upstream provider. That call is treated as another first call, so the results are cached.
 
 If an ingestion job is for an identical geometry, referenced by the same resource ID, and with overlapping time to an already retrieved scene, Azure Data Manager for Agriculture uses the locally stored image. The image isn't downloaded again from the upstream provider. There's no expiration for this pixel-level caching.
 
 ## Satellite sources that Azure Data Manager for Agriculture supports
 
-While Azure Data Manager for Agriculture is in public preview, it supports ingesting data from the Sentinel-2 constellation.
+While Azure Data Manager for Agriculture is in preview, it supports ingesting data from the Sentinel-2 constellation.
 
 ### Sentinel-2
 
@@ -99,7 +99,7 @@ While Azure Data Manager for Agriculture is in public preview, it supports inges
 Sentinel-2 has two products:
 
 * Level 1 data for the top of the atmosphere.
-* Level 2 data for the bottom of the atmosphere. This is an atmospherically corrected variant.
+* Level 2 data for the bottom of the atmosphere. This variant is atmospherically corrected.
 
 Azure Data Manager for Agriculture supports ingesting and retrieving Sentinel_2_L2A and Sentinel_2_L1C data from Sentinel 2.
 

articles/data-manager-for-agri/concepts-ingest-sensor-data.md

@@ -13,8 +13,6 @@ ms.custom: template-concept
 
 Smart agriculture, also known as precision agriculture, allows growers to maximize yields by using minimal resources such as water, fertilizer, and seeds. By deploying sensors, growers and research organizations can begin to understand crops at a micro scale, conserve resources, reduce impact on the environment, and maximize crop yield. Sensors enable important ground-truth data (such as soil moisture, rainfall, and wind speed). This data, in turn, improves the accuracy of recommendations.
 
-[!INCLUDE [public-preview-notice.md](includes/public-preview-notice.md)]
-
 Sensors are of various types:
 
 * Location sensors, which determine latitude, longitude, and altitude
@@ -25,13 +23,15 @@ Sensors are of various types:
 
 There's a large ecosystem of sensor providers that help growers to monitor and optimize crop performance. Sensor-based data also enables an understanding of the changing environmental factors.
 
+[!INCLUDE [public-preview-notice.md](includes/public-preview-notice.md)]
+
 ## How sensors work
 
-Sensors are placed in a field based on its characteristics. Sensors record measurements and transfer the data to the connected node. Each node has one or more sensors connected to it. Nodes equipped with internet connectivity can directly push data to the cloud. Other nodes use an Internet of Things (IoT) agent to transfer data to the gateway.
+Sensors are placed in a field based on its characteristics. Sensors record measurements and transfer the data to the connected node. Each node has one or more sensors connected to it. Nodes equipped with internet connectivity can push data directly to the cloud. Other nodes use an Internet of Things (IoT) agent to transfer data to the gateway.
 
 Gateways collect all essential data from the nodes and push it securely to the cloud via cellular connectivity, Wi-Fi, or Ethernet. After the data resides in a sensor partner's cloud, the sensor partner pushes the relevant sensor data to the dedicated Azure IoT Hub endpoint that Azure Data Manager for Agriculture provides.
 
-In addition to the preceding approach, IoT devices (sensors, nodes, and gateway) can directly push the data to the IoT Hub endpoint. In both cases, the data first reaches IoT Hub, where the next set of processing happens.  
+In addition to the preceding approach, IoT devices (sensors, nodes, and gateway) can push the data directly to the IoT Hub endpoint. In both cases, the data first reaches IoT Hub, where the next set of processing happens.  
 
 :::image type="content" source="./media/sensor-data-flow-new.png" alt-text="Diagram that shows sensor data flow.":::
 
@@ -44,7 +44,5 @@ The following diagram depicts the topology of a sensor in Azure Data Manager for
 ## Next steps
 
 * Learn how to [get started with pushing and consuming sensor data](./how-to-set-up-sensor-as-customer-and-partner.md).
-
 * Learn how to [get started as a customer](./how-to-set-up-sensors-customer.md) to consume sensor data from a supported sensor partner like Davis Instruments.
-
 * Learn how to [get started as a sensor partner](./how-to-set-up-sensors-partner.md) to push sensor data into Azure Data Manager for Agriculture.

articles/data-manager-for-agri/concepts-ingest-weather-data.md

@@ -17,7 +17,7 @@ Azure Data Manager for Agriculture provides current and forecast weather data th
 
 ## Design overview
 
-Azure Data Manager for Agriculture provides weather data through a provider-agnostic approach. You don't have to be familiar with a provider's APIs. Instead, you can use the same Azure Data Manager for Agriculture APIs irrespective of the provider.
+Because Azure Data Manager for Agriculture provides weather data through a provider-agnostic approach, you don't have to be familiar with a provider's APIs. Instead, you can use the same Azure Data Manager for Agriculture APIs irrespective of the provider.
 
 Here are some notes about the behavior of provider-agnostic APIs:
 

articles/data-manager-for-agri/concepts-understanding-throttling.md

@@ -97,10 +97,10 @@ Similarly, for the Basic version, you can perform 5,000,000 (units reset after e
 
 ### How many sensor events can a customer ingest as the maximum number?
 
-The system allows a maximum limit of 100,000 event ingestions per hour. Although new events are continually accepted, there might be a delay in processing. The delay might mean that these events aren't immediately available for real-time egress scenarios alongside the ingestion.
+The system allows a maximum of 100,000 event ingestions per hour. Although new events are continually accepted, there might be a delay in processing. The delay might mean that these events aren't immediately available for real-time egress scenarios alongside the ingestion.
 
 ## Next steps
 
-- [Learn about hierarchy model and how to create and organize your agriculture data](./concepts-hierarchy-model.md)
+- [Learn about the hierarchy model and how to create and organize your agriculture data](./concepts-hierarchy-model.md)
 - [Test the Azure Data Manager for Agriculture REST APIs](/rest/api/data-manager-for-agri)
 - [Learn about common API response headers](/rest/api/data-manager-for-agri/common-rest-response-headers)