[docs] - Clarify explanation of graph-backed assets (#8328)

* clarify explanation of graph-backed assets

* fix typo

* Update docs/content/concepts/assets/software-defined-assets.mdx

Co-authored-by: Erin Cochran <erin.k.cochran@gmail.com>

Co-authored-by: Erin Cochran <erin.k.cochran@gmail.com>

docs/content/concepts/assets/software-defined-assets.mdx

@@ -198,9 +198,9 @@ In this example, Dagster doesn’t need to load data from `upstream_asset` to su
 
 ### Graph-backed assets
 
-[Basic software-defined assets](#a-basic-software-defined-asset) can only produce one data artifact. If generating an asset involves multiple discrete computations, you can use graph-backed assets by separating each computation into an op and building a graph to combine your computations. This way, each discrete computation can be reused in other assets and jobs.
+[Basic software-defined assets](#a-basic-software-defined-asset) are computed using a single op. If generating an asset involves multiple discrete computations, you can use graph-backed assets by separating each computation into an op and building a graph to combine your computations. This allows you to launch re-executions of runs at the op boundaries but doesn't require you to link each intermediate value to an asset in persistent storage.
 
-This approach to asset creation allows you to define a graph of ops which can produce one or multiple assets. **Note**: To use graphs to create an asset, the graph **must return an output**.
+Graph-backed assets are useful if you have an existing graph that produces and consumes assets. Wrapping your graph inside a software-defined asset gives you all the benefits of software-defined assets — like cross-job lineage — without requiring you to change the code inside your graph.
 
 To define a graph-backed asset, use the `from_graph` attribute on the `AssetsDefinition` object: