diff --git a/README.md b/README.md index 7952753..6195377 100644 --- a/README.md +++ b/README.md @@ -2,7 +2,7 @@ > currently available on [arc42.org](https://www.arc42.org) -Site is currently beeing built and served by [Netlify](https://netlify.com) +Site is currently being built and served by [Netlify](https://netlify.com) ### How does it work? diff --git a/_pages/about.md b/_pages/about.md index 74ae0c3..e9a56f0 100644 --- a/_pages/about.md +++ b/_pages/about.md @@ -41,7 +41,7 @@ Read more at [systemsguild.eu](https://systemsguild.eu), [b-agile.de/en](https:/ ### This site... -is maintained on Github, based upon Jekyll, Markdown and other open-source +is maintained on GitHub, based upon Jekyll, Markdown and other open-source technology. It's built using [Netlify](https://www.netlify.com/) and diff --git a/_pages/contact.md b/_pages/contact.md index d7874d4..51ade1e 100755 --- a/_pages/contact.md +++ b/_pages/contact.md @@ -16,15 +16,15 @@ Please note: In case you contact us: * we'll use your personal data (name, email) only for the purpose of answering your request. It will not be stored, kept or processed in sense of European General Data Protection Regulation [GDPR](https://en.wikipedia.org/wiki/General_Data_Protection_Regulation). -* you explicitely give your consent that your data will be used for the +* you explicitly give your consent that your data will be used for the aforementioned objective. -* you explicitely acknowledge and consent that some of the contact options +* you explicitly acknowledge and consent that some of the contact options make use of unencrypted communication channels - therefore your personal data might be visible during transit. -* Email (our adress is spam-protected) +* Email (our address is spam-protected) * via [issue tracker](https://github.com/arc42/arc42-template/issues) at [https://github.com/arc42/arc42-template/issues](https://github.com/arc42/arc42-template/issues). * on LinkedIn: diff --git a/_pages/download.md b/_pages/download.md index e5748e3..636d415 100644 --- a/_pages/download.md +++ b/_pages/download.md @@ -61,7 +61,7 @@ various [formats]({{page.url}}#format-overview) for various tools. For an overvi # File-based formats -These formats are generated based upon their AsciiDoc sources from the [Github repository](https://github.com/arc42/arc42-template). +These formats are generated based upon their AsciiDoc sources from the [GitHub repository](https://github.com/arc42/arc42-template). {% assign formats = "docx|asciidoc|markdown|markdownMP|markdownStrict|markdownMPStrict|gitHubMarkdown|gitHubMarkdownMP|latex|html|rst|textile" | split: "|" %} {% assign types = "plain|withhelp" | split: "|" %} @@ -104,7 +104,7 @@ It is based upon an older version of the template - due to technical difficultie * If you consider to use confluence, the [asciidoc2confluence](https://github.com/rdmueller/asciidoc2confluence) script might be helpful. -* There is also a [confluence plugin available from the atlassian market place](https://marketplace.atlassian.com/plugins/com.networkedassets.plugins.space-blueprint/server/overview). +* There is also a [confluence plugin available from the atlassian marketplace](https://marketplace.atlassian.com/plugins/com.networkedassets.plugins.space-blueprint/server/overview). ## Legacy Version (arc42 v6) for Confluence diff --git a/_pages/more.md b/_pages/more.md index d105082..199c3be 100644 --- a/_pages/more.md +++ b/_pages/more.md @@ -71,7 +71,7 @@ articles_feature: - image_path: /images/publications/article-feature.png alt: "Several magazines" title: "Articles" - excerpt: "More than a hundred articles in various publications (aah - most if that in German)." + excerpt: "More than a hundred articles in various publications (aah - most of that in German)." url: /articles btn_label: "more ..." btn_class: "btn--primary" diff --git a/_pages/overview.md b/_pages/overview.md index 46fdc06..bd45f2d 100644 --- a/_pages/overview.md +++ b/_pages/overview.md @@ -169,7 +169,7 @@ arc42 answers the following two questions in a pragmatic way and can be tailored
2. Constraints
- External systems & interfaces + Regulations and external constraints
@@ -178,7 +178,7 @@ arc42 answers the following two questions in a pragmatic way and can be tailored
3. Context & Scope
- Core ideas and solution approaches + External systems & interfaces
@@ -187,7 +187,7 @@ arc42 answers the following two questions in a pragmatic way and can be tailored
4. Solution Strategy
- Structure of source code, modularization (hierarchical) + Core ideas and solution approaches
diff --git a/_pages/principles-of-tech-documentation.md b/_pages/principles-of-tech-documentation.md index 062e2ee..62a72da 100644 --- a/_pages/principles-of-tech-documentation.md +++ b/_pages/principles-of-tech-documentation.md @@ -180,7 +180,7 @@ Teams must constantly adapt (_maintain_) their documentation, so it remains corr * If the answer to one of these questions is "no", then remove the corresponding part of the documentation. As everything is [version controlled](#sect-version-controlled), it would be available if needed later on. * Optimize your documentation (not only your system!) for maintainability. The section on [Easy to find](#sect-maintainable) contains numerous approaches that help to optimize maintainability. -* [Automate the generation of certain parts](#sect-automate-certain-parts) of your documentation.. +* [Automate the generation of certain parts](#sect-automate-certain-parts) of your documentation.

Req-3: Understandable

@@ -393,7 +393,7 @@ interested in. Referenceable elements can be uniquely identified in the context of your documentation. Instead of writing “see the diagram below” or “the table above”, you should strive for “see diagram 5.2” or “the table 3.1”. You -can chose any numbering or referencing scheme you like, but you should +can choose any numbering or referencing scheme you like, but you should use it consistently. #### How to make documentation referenceable @@ -548,7 +548,7 @@ coverage of automated (*living*) documentation. > users can find the information that they need. > [^hargisDevelopingQualityTechnical2004], p.213 -This requirements relates to both the content of the documentation and +These requirements relate to both the content of the documentation and to the documentation itself. In reality, documentation is often located in access-controlled areas that are not covered by any search engine: That means you have to know where to look for the documentation. @@ -602,7 +602,7 @@ But in reality that’s not always as simple as it sounds: - Documentation authors, especially from non-technical roles, might not be able (or refuse to) use a VCS. -Therefore I propose the following strategy: +Therefore, I propose the following strategy: - Ideally, add all documentation artifacts to a VCS, like `git`. Your VCS should facilitate branching and merging artifacts. Additionally, diff --git a/_pages/why.md b/_pages/why.md index 18aefa4..dff20de 100644 --- a/_pages/why.md +++ b/_pages/why.md @@ -17,7 +17,7 @@ about software architecture is hidden in single brains, scattered code or simply lost. Several typical problems hinder many software projects - which -arc42 can help to reduce or eliminate very effiently with low effort. +arc42 can help to reduce or eliminate very efficiently with low effort. ### Not Existing or Outdated The first problem is missing or outdated documentation: @@ -27,7 +27,7 @@ The first problem is missing or outdated documentation: There's documentation, created somewhere in the past. Rumors say it had been correct a long time ago, the original authors unknown or vanished. Such _historical_ -artifacts only waste disk space and provide no value at alll, for nobody. +artifacts only waste disk space and provide no value at all, for nobody. diff --git a/assets/css/button.css b/assets/css/button.css index bda3efa..1193e27 100644 --- a/assets/css/button.css +++ b/assets/css/button.css @@ -54,9 +54,7 @@ margin-top: 10px; } - - .buttonCanvas { - width: 90vw; + width: 100%; padding: 20px 0; }