# Copyleaks Phrase Blocklist

**Generated:** 2026-07-27
**Unique phrases:** 103

Do not suggest these phrases or strings in replacement text.

---

| Phrase | Max ratio | Status | Times flagged | Do not suggest (sample) |
|--------|-----------|--------|---------------|------------------------|
| the problem, requirements, | 1363× | blocklist | 1 | the problem, requirements,; D1 documents the use case, the HTTP routes I'll build, an… |
| input handling The | 1108× | blocklist | 1 | input handling The; Rename the section to *"Error responses for bad requests"… |
| amount must be positive | 379× | blocklist | 1 | amount must be positive; Table *Message* column: charge amount must exceed zero (o… |
| MVP scope and | 273× | blocklist | 1 | MVP scope and; State the HTTP-only boundary once in a short *Security / … |
| curl, Postman, or | 235× | blocklist | 1 | curl, Postman, or; You can hit the endpoints from the command line or from a… |
| Step 2: split into | 157× | blocklist | 1 | Step 2: split into; Next, separate members who are owed money from members wh… |
| Next steps: implement | 110× | blocklist | 1 | Next steps: implement; What comes after D1: code the API, publish the Swagger fi… |
| with Postman (or curl). | 110× | blocklist | 1 | with Postman (or curl).; using manual HTTP requests (terminal or REST client). |
| OpenAPI Specification 3 (OAS | 90× | blocklist | 1 | OpenAPI Specification 3 (OAS; a Swagger / OAS 3 spec |
| with instructors or peers | 83× | blocklist | 1 | with instructors or peers; with my professor and classmates |
| Common status codes: | 76× | blocklist | 1 | Common status codes:; Typical HTTP responses include: |
| as needed // Step | 64× | blocklist | 1 | as needed // Step; if rounding leaves tiny leftovers // Second phase: |
| simple RESTful API | 52× | blocklist | 1 | simple RESTful API; JSON-over-HTTP API |
| the request body as JSON; | 46× | blocklist | 1 | the request body as JSON;; Step 1 → Decode the incoming payload with json.Unmarshal;… |
| SQLAlchemy / Django ORM | 35× | blocklist | 1 | SQLAlchemy / Django ORM; Python ORM libraries (e.g. SQLAlchemy) |
| invalid input is | 35× | blocklist | 1 | invalid input is; Retitle *"Error-handling pipeline (summary)"* |
| Structure of Programming Language | 32× | persistent | 5 | Structure of Programming Language; Shorten the header to *Course:* CMSC501-1 — Summer 2026 (… |
| or REST client). | 31× | blocklist | 1 | or REST client).; “using manual HTTP requests from a terminal or API testin… |
| or a REST client; | 31× | blocklist | 1 | or a REST client;; “from the command line or an HTTP client app;” |
| input. It returns | 28× | blocklist | 1 | input. It returns; When validation fails, the handler sends a JSON error obj… |
| on the problem definition, | 27× | blocklist | 1 | on the problem definition,; on scoping the problem, the API design, and why I picked … |
| `{"error": "name is required",` | 27× | blocklist | 1 | `{"error": "name is required",`; In the error table, split into columns *Message \| Code* (… |
| Validate required fields | 27× | blocklist | 1 | Validate required fields; Check that required values are present and within allowed… |
| Overkill for a simple | 25× | blocklist | 1 | Overkill for a simple; More stack than I need for a |
| type system / checks | 20× | blocklist | 1 | type system / checks; “Static typing at compile time” (Go column) vs “Dynamic t… |
| empty list i = 0 j = 0 while | 19× | blocklist | 1 | empty list i = 0 j = 0 while |
| validation, the server | 18× | blocklist | 1 | validation, the server; Opening under *Error responses for bad requests → Bad inp… |
| Go garbage collector | 17× | blocklist | 1 | Go garbage collector; Go's built-in GC |
| on the parsed | 17× | blocklist | 1 | on the parsed; Step 2 → After unmarshaling, enforce handler rules on the… |
| rather than crashing the | 17× | blocklist | 1 | rather than crashing the; Opening under *Rejecting bad payloads → Invalid payloads … |
| person p in people | 15× | blocklist | 1 | person p in people; each member in the group |
| could use Python | 15× | blocklist | 1 | could use Python; “FastAPI would work for a small API, but…” |
| cloud load balancer | 15× | blocklist | 1 | cloud load balancer; “a hosted reverse proxy in front of the app).” |
| via terminal commands | 15× | blocklist | 1 | via terminal commands; call the routes with raw JSON over HTTP — e.g. PowerShell… |
| fairly? For instance: | 15× | blocklist | 1 | fairly? For instance:; End the question without "fairly", then break before exam… |
| `"amount must be greater than` | 15× | blocklist | 1 | `"amount must be greater than`; Table row: *Message: amount must be positive · Code:* VAL… |
| Strong fit for | 13× | blocklist | 1 | Strong fit for; Works well for |
| API testing tool. | 12× | blocklist | 1 | API testing tool.; hand-sent JSON over HTTP from PowerShell or a desktop JSO… |
| API in Go | 12× | blocklist | 1 | API in Go; bill-splitting HTTP service written in Go |
| code VALIDATION and | 12× | blocklist | 1 | code VALIDATION and; Replace the long sample sentence with: A zero-amount char… |
| Version control: GitHub | 11× | blocklist | 1 | Version control: GitHub; Repo hosting: GitHub |
| versions, and dependencies | 11× | blocklist | 1 | versions, and dependencies; Python installs, virtualenvs, and package pins |
| to manage and collaborate on. | 11× | blocklist | 1 | to manage and collaborate on.; when more than one person touches the repo. |
| with HTTP status codes. | 11× | blocklist | 1 | with HTTP status codes.; along with the right status code (400, 404, and so on) |
| requests When a request | 11× | blocklist | 1 | requests When a request; Rename section *Rejecting bad payloads and open with Fail… |
| for the chosen language | 10× | blocklist | 1 | for the chosen language; for picking Go over Python and C# |
| coursework and personal | 10× | blocklist | 1 | coursework and personal; class projects and side repos I already use |
| for everyone? Examples: | 10× | blocklist | 1 | for everyone? Examples:; Split into two sentences: “…what balance remains for each… |
| Typing Static typing | 10× | blocklist | 1 | Typing Static typing; Replace the Typing row with a bullet list under *Type che… |
| if CI is | 9× | blocklist | 1 | if CI is; if I add automated tests later, |
| harder to maintain and | 9× | blocklist | 1 | harder to maintain and; tougher to keep consistent and |
| Build the API | 9× | blocklist | 1 | Build the API; Implement the HTTP service |
| Share progress with | 9× | blocklist | 1 | Share progress with; Track milestones using |
| each member in the group | 9× | blocklist | 1 | each member in the group; “for every person loaded from the database” |
| Check that required | 9× | blocklist | 1 | Check that required; Step 2 → Run field and range checks on the parsed struct … |
| simplicity and familiarity | 8× | blocklist | 1 | simplicity and familiarity; I'm already comfortable with it |
| How it works (high | 8× | blocklist | 1 | How it works (high; Flow (high level) |
| would work for a small | 8× | blocklist | 1 | would work for a small; Python's FastAPI could handle this scope, but managing en… |
| small REST API | 7× | blocklist | 1 | small REST API; compact HTTP bill-splitter service |
| and a clear path to | 7× | blocklist | 1 | and a clear path to; and room to grow into |
| the product grows | 7× | blocklist | 1 | the product grows; I need multi-user hosting |
| "person not found | 7× | blocklist | 1 | "person not found; "member not in this group" |
| the API design, and | 7× | blocklist | 1 | the API design, and; “requirements, endpoint layout, and why I chose Go/Fiber” |
| each person still | 6× | blocklist | 1 | each person still; what balance remains for everyone |
| still efficient for | 6× | blocklist | 1 | still efficient for; fast enough for |
| easier to deploy and | 6× | blocklist | 1 | easier to deploy and; simpler to hand off and |
| Python can also | 6× | blocklist | 1 | Python can also; I could use Python (FastAPI) |
| if needed later, | 6× | blocklist | 1 | if needed later,; down the road, |
| .NET runtime environment | 6× | blocklist | 1 | .NET runtime environment; installed .NET SDK/runtime |
| group and returns | 6× | blocklist | 1 | group and returns; group, then outputs |
| at runtime Static | 6× | blocklist | 1 | at runtime Static; Python cell → "Dynamic types — errors often surface when … |
| not found", "code": | 6× | blocklist | 1 | not found", "code":; Use table columns *Message / Code* for 404 rows (e.g. gro… |
| and range checks | 6× | blocklist | 1 | and range checks; Covered by phrase #1 rewrites (remove “range checks” enti… |
| the API. Backend | 5× | blocklist | 1 | the API. Backend; the HTTP layer. Server-side |
| the program Task | 5× | blocklist | 1 | the program Task; *Problem / What it solves* |
| end function Example | 5× | persistent | 2 | end function Example; Separate example from code — use a paragraph after the cl…; Close the code block, add a blank line, then a separate p… |
| on the version and | 5× | blocklist | 1 | on the version and; about Python/runtime versions and |
| end if // Step | 5× | blocklist | 1 | end if // Step |
| as the project grows | 5× | blocklist | 1 | as the project grows; as I add milestones |
| (name or ID) and | 5× | blocklist | 1 | (name or ID) and; (display name plus DB id) and |
| REST client or | 5× | blocklist | 1 | REST client or; “HTTP client or” |
| HTTP client or | 5× | blocklist | 1 | HTTP client or; settlement-pairs list you can read in a JSON viewer or la… |
| What each package | 5× | blocklist | 1 | What each package; *Package and type roles* |
| Python and C#)· Go: | 4× | persistent | 2 | Python and C#)· Go:; (Presentation slide only — rewrite slide bullets as full …; Rewrite the slide as full sentences under headings *Go, P… |
| who owes whom | 4× | blocklist | 2 | who owes whom; who should pay whom; (who owes whom) |
| reverse proxy / load balancer). | 4× | blocklist | 1 | reverse proxy / load balancer).; nginx or a cloud load balancer in front of the app). |
| merged into main | 4× | blocklist | 1 | merged into main; merged back to main |
| harder to manage and | 4× | blocklist | 1 | harder to manage and; trickier to package and |
| in memory. 5. Use | 4× | blocklist | 1 | in memory. 5. Use; only in RAM between restarts. For persistence I'll use GO… |
| as the ORM | 4× | blocklist | 1 | as the ORM; for database access |
| (and optionally add | 4× | blocklist | 1 | (and optionally add; (and add a UI later if I want) |
| each id in | 4× | blocklist | 1 | each id in; every participant id in |
| Implement the HTTP | 4× | blocklist | 1 | Implement the HTTP; “Stand up the Go web layer with *Fiber v2*” |
| Parse JSON → if | 4× | blocklist | 1 | Parse JSON → if; Read the request body as JSON; malformed syntax yields 40… |
| Point at 1-2 | 4× | blocklist | 1 | Point at 1-2; Highlight one or two functions on the slide (e.g. CreateC… |
| group not found | 4× | blocklist | 1 | group not found; Table *Message* column: no group with that ID / unknown g… |
| this project plan). | 3× | blocklist | 3 | this project plan).; the MVP scope).; this project plan) |
| for lower memory | 3× | blocklist | 1 | for lower memory; with smaller per-request allocations |
| apps are often | 3× | blocklist | 1 | apps are often; real services are usually |
| or nginx or | 3× | blocklist | 1 | or nginx or; “Fiber ListenTLS, a reverse proxy, or platform-managed TL… |
| remains for each | 3× | blocklist | 1 | remains for each; who still owes money after splitting fairly? |
| response body: ["error": | 3× | blocklist | 1 | response body: ["error":; *Sample validation failure:* |
| from different inputs | 3× | blocklist | 1 | from different inputs; *Sample runs — good requests and failures* |

---

## Full blocklist strings

- .NET runtime environment
- “a hosted reverse proxy in front of the app).”
- “FastAPI would work for a small API, but…”
- “Fiber ListenTLS, a reverse proxy, or platform-managed TLS).”
- “for every person loaded from the database”
- “from the command line or an HTTP client app;”
- “HTTP client or”
- "member not in this group"
- "person not found
- “requirements, endpoint layout, and why I chose Go/Fiber”
- “Stand up the Go web layer with *Fiber v2*”
- “Static typing at compile time” (Go column) vs “Dynamic typing; bugs may surface at runtime” (Python) vs “Static types on the CLR” (C#).
- “using manual HTTP requests from a terminal or API testing tool).”
- (and add a UI later if I want)
- (and optionally add
- (display name plus DB id) and
- (name or ID) and
- (Presentation slide only — rewrite slide bullets as full sentences, not compressed )· Go: notation.)
- (settlement pairs)
- (who owes whom)
- *Package and type roles*
- *Problem / What it solves*
- *Sample runs — good requests and failures*
- *Sample validation failure:*
- `"amount must be greater than`
- `{"error": "name is required",`
- a Swagger / OAS 3 spec
- about Python/runtime versions and
- along with the right status code (400, 404, and so on)
- amount must be positive
- and a clear path to
- and range checks
- and room to grow into
- API in Go
- API testing tool.
- apps are often
- as I add milestones
- as needed // Step
- as the ORM
- as the project grows
- at runtime Static
- bill-splitting HTTP service written in Go
- Build the API
- call the routes with raw JSON over HTTP — e.g. PowerShell Invoke-RestMethod or a desktop JSON tool
- Check that required
- Check that required values are present and within allowed ranges
- class projects and side repos I already use
- Close the code block, add a blank line, then a separate paragraph: *Worked example:* Dinner $90…
- cloud load balancer
- code VALIDATION and
- Common status codes:
- compact HTTP bill-splitter service
- could use Python
- coursework and personal
- Covered by phrase #1 rewrites (remove “range checks” entirely).
- curl, Postman, or
- D1 documents the use case, the HTTP routes I'll build, and my Go/Fiber choice — not working code yet.
- down the road,
- each id in
- each member in the group
- each person still
- easier to deploy and
- empty list i = 0 j = 0 while
- end function Example
- end if // Step
- End the question without "fairly", then break before examples — e.g. "which members still owe money once shares are applied?" Add a blank line, then *Two examples:* (not "For instance:").
- every participant id in
- fairly? For instance:
- fast enough for
- Flow (high level)
- for database access
- for everyone? Examples:
- for lower memory
- for picking Go over Python and C#
- for the chosen language
- from different inputs
- Go garbage collector
- Go's built-in GC
- group and returns
- group not found
- group, then outputs
- hand-sent JSON over HTTP from PowerShell or a desktop JSON viewer.
- harder to maintain and
- harder to manage and
- Highlight one or two functions on the slide (e.g. CreateCharge, settle.Compute)
- How it works (high
- HTTP client or
- I could use Python (FastAPI)
- I need multi-user hosting
- I'm already comfortable with it
- if CI is
- if I add automated tests later,
- if needed later,
- if rounding leaves tiny leftovers // Second phase:
- Implement the HTTP
- Implement the HTTP service
- in memory. 5. Use
- In the error table, split into columns *Message | Code* (e.g. name is required | VALIDATION) instead of repeating the full JSON blob on every row.
- input handling The
- input. It returns
- installed .NET SDK/runtime
- invalid input is
- JSON-over-HTTP API
- merged back to main
- merged into main
- More stack than I need for a
- MVP scope and
- MVP scope)
- Next steps: implement
- Next, separate members who are owed money from members who owe money.
- nginx or a cloud load balancer in front of the app).
- not found", "code":
- on scoping the problem, the API design, and why I picked Go/Fiber
- on the parsed
- on the problem definition,
- on the version and
- only in RAM between restarts. For persistence I'll use GORM —
- OpenAPI Specification 3 (OAS
- Opening under *Error responses for bad requests → Bad input never kills the process—I write a structured error object back to the client.*
- Opening under *Rejecting bad payloads → Invalid payloads get a JSON error body—the process keeps running.*
- or a REST client;
- or nginx or
- or REST client).
- Overkill for a simple
- Parse JSON → if
- person p in people
- Point at 1-2
- Python and C#)· Go:
- Python can also
- Python cell → "Dynamic types — errors often surface when the service is running" (keep C# cell separate).
- Python installs, virtualenvs, and package pins
- Python ORM libraries (e.g. SQLAlchemy)
- Python's FastAPI could handle this scope, but managing environments…
- rather than crashing the
- Read the request body as JSON; malformed syntax yields 400 BAD_REQUEST
- real services are usually
- remains for each
- Rename section *Rejecting bad payloads and open with Failed checks return JSON errors rather than crashing the process* (drops “request” repetition).
- Rename the section to *"Error responses for bad requests" and open with: When a request fails validation, the server answers with JSON instead of crashing.*
- Replace the long sample sentence with: A zero-amount charge returns HTTP 400; the body carries a VALIDATION code and a short amount-related message.
- Replace the Typing row with a bullet list under *Type checking:* — Go: compile-time checks; Python: types resolved when code runs; C#: CLR static types.
- Repo hosting: GitHub
- requests When a request
- response body: ["error":
- REST client or
- Retitle *"Error-handling pipeline (summary)"*
- reverse proxy / load balancer).
- Rewrite the slide as full sentences under headings *Go, Python, C#* — no compressed )· notation.
- Separate example from code — use a paragraph after the closing end function instead of inline "Example:".
- settlement-pairs list you can read in a JSON viewer or later in a browser UI.
- Share progress with
- Shorten the header to *Course:* CMSC501-1 — Summer 2026 (drop the long official title).
- simple RESTful API
- simpler to hand off and
- simplicity and familiarity
- small REST API
- Split into two sentences: “…what balance remains for each person?” then start examples on the next line with “For instance,” or “Two cases:”.
- SQLAlchemy / Django ORM
- State the HTTP-only boundary once in a short *Security / transport* note near the top, then drop repeated “MVP scope” wording elsewhere — e.g. “Local dev uses plain HTTP; TLS is a later deployment concern.”
- Step 1 → Decode the incoming payload with json.Unmarshal; syntax errors return 400 BAD_REQUEST.
- Step 2 → After unmarshaling, enforce handler rules on the struct (empty names, amount > 0, etc.) → 400 VALIDATION
- Step 2 → Run field and range checks on the parsed struct → 400 VALIDATION
- Step 2: split into
- still efficient for
- Strong fit for
- Structure of Programming Language
- Table *Message* column: charge amount must exceed zero (or non-positive amount rejected) — update the fenced JSON example to match only if your Go handler returns the same string; otherwise drop the example and describe the rejection in prose.
- Table *Message* column: no group with that ID / unknown group ID (only if you are willing to change handler copy; otherwise keep API truth and accept the flag).
- Table row: *Message: amount must be positive · Code:* VALIDATION (no quoted JSON string).
- the API design, and
- the API. Backend
- the HTTP layer. Server-side
- the MVP scope).
- the MVP write-up
- the problem, requirements,
- the product grows
- the program Task
- the request body as JSON;
- this project plan
- this project plan)
- this project plan).
- to manage and collaborate on.
- tougher to keep consistent and
- Track milestones using
- trickier to package and
- type system / checks
- Typical HTTP responses include:
- Typing Static typing
- Use table columns *Message / Code* for 404 rows (e.g. group not found | NOT_FOUND).
- using manual HTTP requests (terminal or REST client).
- Validate required fields
- validation, the server
- Version control: GitHub
- versions, and dependencies
- via terminal commands
- what balance remains for everyone
- What comes after D1: code the API, publish the Swagger file, and tag milestones in the repo.
- What each package
- when more than one person touches the repo.
- When validation fails, the handler sends a JSON error object and the matching status code.
- who owes whom
- who should pay whom
- who still owes money after splitting fairly?
- with HTTP status codes.
- with instructors or peers
- with my professor and classmates
- with Postman (or curl).
- with smaller per-request allocations
- Works well for
- would work for a small
- You can hit the endpoints from the command line or from a REST client — no UI required yet.