Streamline name casing in README

[kristiandupont]

As per this suggestion, I did a quick scan through the README and streamlined all name casing: schemas are camelCased, types are PascalCased.

[netlify]

✅ Deploy Preview for guileless-rolypoly-866f8a ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	366a85e
🔍 Latest deploy log	https://app.netlify.com/sites/guileless-rolypoly-866f8a/deploys/65e08ab8c5d8be00084500ec
😎 Deploy Preview	https://deploy-preview-3285--guileless-rolypoly-866f8a.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[colinhacks]

In a lot of cases I'm partial to Pascal-casing, since schemas ultimately represent types. This also enables a pattern that I personally love where a schema and it's inferred type can share a name. They are the runtime & static representation of the same type, so this feels right to me.

const Dog = z.object({
  name: z.string(),
  age: z.number(),
});

type Dog = z.infer<typeof Dog>

But for utility schemas with a self-evident static type I wouldn't capitalize.

const nonemptyString = z.string().min(1)

That's what I do and what feels natural to me within TypeScript norms.

I appreciate the PR, but a lot of the changes in this PR feel weird to me so I'm not going to merge. Ultimately people can do what they want and I don't think there's much value in trying to establish a dogma here.