# How do I make it use don't punctuation? **URL:** \ **Category:** API\ **Created:** [October 2, 2023, 12:49pm UTC](https://community.openai.com/t/how-do-i-make-it-use-dont-punctuation/408708 "2023-10-02T12:49:25Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![posegraphic](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/posegraphic/32/211592_2.png) [@posegraphic](https://community.openai.com/u/posegraphic)\ **Post date:** [October 2, 2023, 12:49pm UTC](https://community.openai.com/t/how-do-i-make-it-use-dont-punctuation/408708/1 "2023-10-02T12:49:25Z")
I tell him to make punctuation and sometimes spelling mistakes, but he doesn’t. I say it don’t put a comma, don’t put a dot, it’s doing it out of spite 🙂 sorry for my bad english ---
**Author:** ![VeitB](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/veitb/32/712987_2.png) [@VeitB](https://community.openai.com/u/VeitB)\ **Post date:** [October 2, 2023, 1:02pm UTC](https://community.openai.com/t/how-do-i-make-it-use-dont-punctuation/408708/2 "2023-10-02T13:02:15Z")
Hi! And welcome to the community! You can try giving a few examples with spelling errors as examples in the prompt. I am suggesting this because it’s actually quite easy to create such a persona but when the model starts making mistakes on purpose the whole reply becomes quite random. [https://chat.openai.com/share/0e9a818b-f960-4d5c-863b-a0e222eecd75](https://chat.openai.com/share/0e9a818b-f960-4d5c-863b-a0e222eecd75) You can try to integrate this approach with your prompt and see what happens. ---
**Author:** ![bill.french](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/bill.french/32/15015_2.png) [@bill.french](https://community.openai.com/u/bill.french)\ **Post date:** [October 2, 2023, 4:48pm UTC](https://community.openai.com/t/how-do-i-make-it-use-dont-punctuation/408708/3 "2023-10-02T16:48:15Z")
This is similar to a prompt that returns EU formatted numbers. In a recent thread I was following about a no/low-code platform that did not support EU number formats, participants claimed generative AI wasn’t precise enough to format numbers into the EU rendering equivalent - i.e., $2,192.45 → $2.192,45. [This document](https://coda.io/d/_dFNQGH_gvNo/US-to-EU-Currency-Formatting_suAAW) demonstrates the prompt I used and applied to 1,080 random tests. The results of all 1,080 tests are perfect. The test sample size is statistically meaningful. > **[Deterministic AI](https://impertinent.substack.com/p/deterministic-ai)** > > Generative AI has a PR problem. ChatGPT made it easy to demonstrate how dumb it could be. TL;DR Here’s the [Coda](https://coda.grsm.io/qwuhtmq425oh) prompt I used to compel the LLM to be consistent. ![image](https://us1.discourse-cdn.com/openai1/original/3X/7/b/7b6b10e4a568d5afe54fbed03d24749fb5933949.png) ---
**Author:** ![\_j](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/_j/32/766292_2.png) [@\_j](https://community.openai.com/u/_j)\ **Post date:** [October 2, 2023, 4:54pm UTC](https://community.openai.com/t/how-do-i-make-it-use-dont-punctuation/408708/4 "2023-10-02T16:54:29Z")
> How do I make it use don’t punctuation? Search Keywords: gpt “fine-tune” copy my “writing style” - depending on if this is actually an API category question. ---
**Author:** ![VeitB](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/veitb/32/712987_2.png) [@VeitB](https://community.openai.com/u/VeitB)\ **Post date:** [October 2, 2023, 5:04pm UTC](https://community.openai.com/t/how-do-i-make-it-use-dont-punctuation/408708/5 "2023-10-02T17:04:26Z")
Good analogy and thanks for sharing! I believe this case is a little tricky when trying to fine-tune the prompt to the desired amount and types of errors because for my personal taste “famus” instead of “famous” is a bit much of an error. Applying your straightforward solution yields this result in ChatGPT 3.5: [https://chat.openai.com/share/1b8f9f89-fc74-4bc7-9b95-3574dda21f2b](https://chat.openai.com/share/1b8f9f89-fc74-4bc7-9b95-3574dda21f2b) Works well and should be easy to implement for OP. PS. The shirty typo is my own fault.