4 ms·
I was thinking specifically of this rule. Their original title was misleading, implying broader scope, all dynamic DHCP. Narrowing to saying Microsoft DHCP se
by Terretta 3y ago
I was thinking specifically of this rule.
Their original title was misleading, implying broader scope, all dynamic DHCP. Narrowing to saying Microsoft DHCP seemed less misleading and less click-bait. I could picture a pile of conversation saying "oh, this is just X" so tried to narrow it to just X.
From your comment, I take it I saw it wrong. Just saying that rule was my specific reason for the edit, to make less click-bait and less misleading.
- dang 3y agoIf you were thinking of the rule and trying to abide by it, that's more than enough! This domain (titles etc.) is complex enough that it's totally normal for people to interpret the rule differently.