Fix typos and change some grammatical constructions

This commit is contained in:
daniel.motzko
2021-07-02 13:54:18 +02:00
parent ea00db0ac6
commit 51c8a54795
54 changed files with 185 additions and 152 deletions

View File

@@ -31,7 +31,7 @@ Flamingo has a clean architecture with clear dependencies in mind and offers a t
* GraphQL support and therefore support to build nice SPA and PWAs on top of it
* Resilience and Caching for external APIs calls.
Flamingo itself does not contain ORM Mapper or libraries - instead it emphasizes ["ports and adapters"](/methods-and-patterns/ports-and-adapters.html) architecture - so that you have a technology free (domain) model and any possible (and replaceable) persistence behind it.
Flamingo itself does not contain ORM Mapper or libraries - instead it emphasizes ["ports and adapters"](/methods-and-patterns/ports-and-adapters.html) architecture - so that you have a technology free (domain) model and any possible (and replaceable) persistence behind it.
That makes Flamingo useful to build microservices and applications - especially to build "frontends" or portals that require interaction with other (micro) services in a distributed architecture.
When sticking to the architectural recommendation, you can build modular applications with replaceable adapters that gives you independent testability.

View File

@@ -7,7 +7,7 @@ quadrant: languages-and-frameworks
Kotlin is used successfully in production by multiple teams.
Kotlin is 100% interoperable with Java. It means the code can live side-by-side in one code base and interact.
From the beginning it was designed with practical thought in mind. So the IDE Support in IntelliJ is really great.
From the beginning it was designed with practical thought in mind. So the IDE Support in IntelliJ is really great.
The Spring Framework Developer put a lot of effort that Springs play well together with Kotlin.

View File

@@ -4,6 +4,6 @@ ring: hold
quadrant: languages-and-frameworks
---
Since the RAML project has decided to [join](https://blogs.mulesoft.com/dev/api-dev/open-api-raml-better-together/) the OpenAPI initiative and the RAML ecosystem lacks further development and additional tools, we decided to use and recommend using ["OpenAPI specification (OAS)"](/tools/open-api.html) as description standard instead.
Since the RAML project has decided to [join](https://blogs.mulesoft.com/dev/api-dev/open-api-raml-better-together/) the OpenAPI initiative and the RAML ecosystem lacks further development and additional tools, we decided to use and recommend using ["OpenAPI specification (OAS)"](/tools/open-api.html) as description standard instead.
RAML still provides advantages in modeling an API through it's more expressive modeling language and can produce OAS

View File

@@ -5,5 +5,5 @@ quadrant: tools
---
[Hashicorp Vault](https://www.vaultproject.io/) is a Go application with a Rest/Cli interface that you can use to securely access secrets.
A secret can be any sensitive data, such as credentials, certificates, access tokens, encryption keys etc.
A secret can be any sensitive data, such as credentials, certificates, access tokens, encryption keys etc.
Vaults key features are a secure secret storage, dynamic secretes (create on-demand secrets), data encryption, secret leasing, renewal and revocation.