References: Hyphenated "Architecture-as-Code" used outside FINOS project name

Open Beginner friendly
#1,867 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Quiet
Domain
documentation

Research direction

Start by reading the specified lines in docs/33_references.md, docs/06_structurizr.md, docs/31_appendix_b_technical_architecture.md, and docs/19_management_as_code.md. Compare each occurrence with the Style Guide rule, preserving proper-noun titles and URLs while changing surrounding prose to “Architecture as Code” or the italicised repository slug. Done means all affected prose follows the stated convention.

Written by the indexing model from the issue text.

Description

documentation language

Category: style / references
Severity: low

Problem

The hyphenated form "Architecture-as-Code" is reserved for the FINOS project slug only. Using it in prose contradicts the Style Guide's "always write Architecture as Code" rule.

Affected files

  • docs/33_references.md:33 ("GDPR for Organisations" cites a URL containing /for-organizations/ — URL fine, but "organisations" vs "organizations" inside title could be clarified)
  • docs/33_references.md:42
  • docs/06_structurizr.md:1278
  • docs/31_appendix_b_technical_architecture.md:67, 323
  • docs/19_management_as_code.md:59

Suggested fix

Retain "Architecture-as-Code" inside proper-noun project titles and URLs. In surrounding prose, refer to "the FINOS Architecture as Code project" or "the architecture-as-code repository" (italicised, as a code-slug reference).


Auto-generated by editorial review agent.

Dominant language
Python
Stars
4
Forks
0
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Geonitab/architecture_as_code

All issues in Geonitab/architecture_as_code

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.