multiple glossery entries for `universes`

[ZZiigguurraatt]

We have two different glossary entries for universes.

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

Lines 166 to 170 in 0ba7c3c

	## Universe
	A universe is a server that serves information about assets and their transfers. Universes can also be used to transfer proof files between users.

docs.lightning.engineering/community-resources/glossary.md

Lines 632 to 636 in 0ba7c3c

	## Universe <a href="#docs-internal-guid-ed1dfbe4-7fff-b3c7-6199-85713fa053a6" id="docs-internal-guid-ed1dfbe4-7fff-b3c7-6199-85713fa053a6"></a>
	A universe is a repository for [Taro](glossary.md#docs-internal-guid-7cc2614e-7fff-6a58-76d9-4f295cc1a60e) assets. It serves information such as metadata and proofs to prospective and existing users and holders of such assets.

We also have a FAQ item with with slightly different text.

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

Lines 38 to 42 in 0ba7c3c

	### What is a universe?
	A Taproot Assets universe is a repository of assets and their proofs. A universe may serve information about a single or multiple asset types (e.g. a specific stablecoin or all stablecoins). It may hold information about which assets have been issued, their quantity, and rules as well as hold proofs about recent transfers. The criteria for releasing this information is up to a universe or universe operator.

Seems like there should only be one, or at least have identical text in each location. Also, would it be better to link to

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

Lines 166 to 178 in 0ba7c3c

	### The Universe <a href="#docs-internal-guid-81622115-7fff-548d-5594-a7c4b43b97b3" id="docs-internal-guid-81622115-7fff-548d-5594-a7c4b43b97b3"></a>
	A Universe is a service that provides information about assets as well as proofs for asset holders. It acts similarly to a bitcoin block explorer, but showcases Taproot Assets transaction data which is stored off-chain with Taproot Assets clients. The main difference is that, as most information related to Taproot Assets is off-chain, it is easier to conceal.
	A Universe may be run by the asset issuer themselves or may be appointed by an issuer. It is also conceivable that community-run Universes aggregate information submitted by asset holders.
	Given a known asset ID, the Universe for example may provide information about its Genesis output, as well as current meta information such as documentation, asset scripts or total coins in circulation. A service may also know about multiple assets (Multiverse) or only about a single output (Pocket Universe).
	A Universe has no privileges within the Taproot Assets Protocol. It produces transaction data validated against the bitcoin blockchain. An adversarial Universe could only refrain from returning data requested by clients. Taproot Assets transaction data isn’t bound to a Universe. The data availability offerings provided by a Universe is motivated by entities who wish to have fast, cheap verification of their Taproot Assets.
	[Read the BIPs: Taproot Asset Universes](https://github.com/Roasbeef/bips/blob/bip-tap/bip-tap-universe.mediawiki)

in the short definition so someone can know where to find more detailed information?