clearly define genesis point and anchor outpoint

[ZZiigguurraatt]

ListAssets (https://lightning.engineering/api-docs/api/taproot-assets/taproot-assets/list-assets) yields a genesis_point (https://github.com/lightninglabs/taproot-assets/blob/ee06af74d45a5eb37887876972ebaf2223fd8a82/taprpc/taprootassets.proto#L229-L230) and anchor_outpoint (https://github.com/lightninglabs/taproot-assets/blob/ee06af74d45a5eb37887876972ebaf2223fd8a82/taprpc/taprootassets.proto#L202-L203).

genesis_point is defined (

docs.lightning.engineering/the-lightning-network/taproot-assets/glossary.md

Lines 55 to 57 in dede15c

	## Genesis point
	The genesis point is the first input of the transaction that mints a Taproot Asset.

), but it would be good to include this visually showing a transaction with multiple inputs. On https://docs.lightning.engineering/the-lightning-network/taproot-assets/taproot-assets-protocol there is a mention of a genesis_outpoint and a genesis output, but it is unclear if those are the same as genesis_point.

We have Anchor defined (

docs.lightning.engineering/the-lightning-network/taproot-assets/glossary.md

Lines 9 to 11 in dede15c

	## Anchor <a href="#docs-internal-guid-85ae5d8e-7fff-f351-537f-243d2bc233ca" id="docs-internal-guid-85ae5d8e-7fff-f351-537f-243d2bc233ca"></a>
	The anchor transaction is the Bitcoin transaction that mints or transfers a Taproot Asset.

), but it is unclear if that is the same thing as an anchor_outpoint. There is no mention of anchor on https://docs.lightning.engineering/the-lightning-network/taproot-assets/taproot-assets-protocol .

Please explain, is a genesis_point a special type of anchor_outpoint? What is an anchor_outpoint called once the asset has been transferred?

It would be nice to see the genesis point and anchor outpoint clearly defined on https://docs.lightning.engineering/the-lightning-network/taproot-assets/taproot-assets-protocol using figures so that one can visually understand how to properly interpret the response of the ListAssets RPC and understand how taproot assets are actually created and moved around using tapd. Also, having consistent names and descriptions in .proto comments/documentation, glossary, and general documentation helps to know you are connecting all documentation sources together properly.