xpub – Is the trailing pathing in multi-sig descriptors necessary?

I created a multisig wallet with BlueWallet, and I want to convert the config file to a descriptor:

Name: Multisig Vault
Policy: 2 of 3
Derivation: m/48’/0’/0’/2′
Format: P2WSH

1E74CA69: xpub65……………………Qwg1Wd

9F40E694: xpub74hnJ……………………cWoEszidc

derivation: m/48’/0’/2’/2′
B5B630B5: xpub6F9A……………………Rb1VjK

I see in the docs that when making a wsh(sortedmulti()) descriptor, the keys usually have trailing pathing (example: [e6807791/44h/1h/0h]tpubDDAfvogaaAxaFJ6c15ht7Tq6ZmiqFYfrSmZsHu7tHXBgnjMZSHAeHSwhvjARNA6Qybon4ksPksjRbPDVp7yXA1KjTjSd5x18KHqbppnXP1s/0/* —> Here I am talking about the /0/*). I also saw in the docs that you want to make 2 descriptors; 1 for change addresses and 1 for regular addresses : "Now the multisig is created by importing the external and internal descriptors: wsh(sortedmulti(,XPUB1/0/*,XPUB2/0/*,…,XPUBN/0/*)) and wsh(sortedmulti(,XPUB1/1/*,XPUB2/1/*,…,XPUBN/1/*)) (one descriptor w/ 0 for receiving addresses and another w/ 1 for change)." Is that true? Or can I just ignore completely the trailing pathing and just do:

wsh(sortedmulti(2,[1E74CA69/48’/0’/0’/2′]xpub65……………………Qwg1Wd,[9F40E694/48’/0’/0’/2′]xpub74hnJ……………………cWoEszidc,[B5B630B5/48’/0’/2’/2′]xpub6F9A……………………Rb1VjK))