Nebular
Chieftain
http://www.dndjunkie.com/civilopedia/vanilla/POLICY_COLLECTIVE_RULE.aspx
In the vanilla game, Collective Rule doesn't have any prerequisites so it appears as the first item. With the G+K expansion, Collective Rule first requires Republic, so it appears as the second item. In both cases, however, Collective Rule's description should read "Speeds the training of Settlers by 50% in the Capital and a free Settler appears near the Capital." The "Newly founded cities" description you're getting is from an older version of the game. Steam should automatically update the game to the latest version. You may need to have it re-validate the game files (right-click the game, choose Properties, and it should be on one of the tabs) to make it re-check everything. I know that the Mac version of the game is slightly behind when it comes to receiving patches. I'm not sure where they're currently at as far as version number. So if you're playing on a Mac, that might explain the mismatch as well (though I was sure they had at least caught up to the version where that policy info changed).
In the vanilla game, Collective Rule doesn't have any prerequisites so it appears as the first item. With the G+K expansion, Collective Rule first requires Republic, so it appears as the second item. In both cases, however, Collective Rule's description should read "Speeds the training of Settlers by 50% in the Capital and a free Settler appears near the Capital." The "Newly founded cities" description you're getting is from an older version of the game. Steam should automatically update the game to the latest version. You may need to have it re-validate the game files (right-click the game, choose Properties, and it should be on one of the tabs) to make it re-check everything. I know that the Mac version of the game is slightly behind when it comes to receiving patches. I'm not sure where they're currently at as far as version number. So if you're playing on a Mac, that might explain the mismatch as well (though I was sure they had at least caught up to the version where that policy info changed).