Language check for PR #2962 (#3156)

articles/hilla/lit/start/faq.adoc

@@ -8,7 +8,6 @@ order: 50
 
 = FAQ
 
-pass:[<!-- vale Vaadin.HeadingCase = NO -->]
 
 == What is Hilla?
 
@@ -25,7 +24,7 @@ Hilla is designed to be simple enough for small utilities, but robust enough to
 The automatic type generation ensures that your frontend and backend always stay in sync and that you catch mistakes at build time, not runtime.
 
 
-== What are the benefits of using Hilla?
+== What are the Benefits of Using Hilla?
 
 Hilla simplifies the process of creating business applications. It has many benefits:
 
@@ -36,41 +35,41 @@ Hilla simplifies the process of creating business applications. It has many bene
 - Gets you started quickly with a zero-configuration toolchain for building both your frontend and backend.
 
 
-== Hilla made for whom?
+== Hilla is Made for Whom?
 
 Hilla provides a simpler way to build complex business applications. A smaller team, or even a solo developer, can build the full stack, instead of having separate frontend and backend teams synchronizing their work. Hilla is also made for those who value open-source transparency together with the option of first-party support for their business.
 
 
-== Who is behind Hilla?
+== Who's Behind Hilla?
 
 Hilla is made and maintained by https://vaadin.com[Vaadin], the company behind the top Java web framework and corresponding tools and components for over 20 years.
 
 
-== Is Hilla open source?
+== Is Hilla Open Source?
 
 Yes, Hilla is Apache 2.0 licensed. Hilla is hosted in a public https://github.com/vaadin/hilla[GitHub repository] where you can view, extend and modify the source code and report issues.
 
 
-== Can I get enterprise support for Hilla?
+== Is there Enterprise Support for Hilla?
 
 Hilla is supported by Vaadin. All the commercial support, components, warranty, and services apply to Hilla. See the https://vaadin.com/pricing/hilla[Vaadin pricing page] for details.
 
 
 ifdef::hilla-lit[]
-== How is Hilla different from React?
+== How is Hilla Different from React?
 
 Hilla has a component model that's similar to React, using the https://lit.dev/[Lit] library. However, you can also https://hilla.dev/docs/react[use React] instead of Lit together with Hilla. What makes Hilla different from React is that it includes both the frontend and Java backend in the same project. Hilla includes everything you need to build an application in one package: UI components, routing, forms, security, build tooling. You can get first-party support for using Hilla from Vaadin, the company that built it.
 endif::hilla-lit[]
 
 
 ifdef::react[]
-== Can I use other React components with Hilla?
+== Can I use Other React Components with Hilla?
 
 Yes, you can use any React components with Hilla, install them with npm and import them in your component as normal.
 endif::react[]
 
 
-== How is Hilla different from Angular?
+== How is Hilla Different from Angular?
 
 Angular is a frontend framework for mobile and desktop applications with modules, dependency injection, and other features that enterprise application developers are used to.
 
@@ -80,7 +79,7 @@ endif::hilla-lit[]
 Unlike Angular, Hilla includes both the frontend and Java backend in the same project. Hilla includes everything you need to build an application in one package: UI components, routing, forms, security, build tooling. You can get first-party support for using Hilla from Vaadin, the company that built it.
 
 
-== How does Hilla differ from Vue?
+== What's the Difference Between Hilla and Vue?
 
 Vue.js is a lightweight frontend framework with a framework-specific component model.
 
@@ -90,7 +89,7 @@ endif::hilla-lit[]
 Unlike Vue, Hilla includes both the frontend and Java backend in the same project. Hilla includes everything you need to build an application in one package: UI components, routing, forms, security, build tooling. You can get first-party support for using Hilla from Vaadin, the company that built it.
 
 
-== How is Hilla different from JHipster?
+== How does Hilla Compare to JHipster?
 
 JHipster provides a set of tools for generating full-stack web applications and microservices by combining a Java Spring backend with a React/Angular/Vue frontend.
 
@@ -103,23 +102,23 @@ endif::react[]
 It includes UI components, routing, forms, security, and build tooling. As the framework is updated, the Hilla development team ensures that the different parts of it remain interoperable, and offer documentation for upgrading when needed.
 
 
-== Can I use Jakarta EE or Quarkus instead of Spring Boot?
+== Can Jakarta EE or Quarkus Replace Spring Boot?
 
 Neither Jakarta EE nor Quarkus support is on the roadmap. If you're interested in using either technology, show your interest in https://github.com/vaadin/hilla/issues/211[this GitHub issue]. If there is enough demand, that gives the development team some guidance to adjust the priorities.
 
 
-== Does Hilla work with multi-module projects?
+== Does Hilla Work with Multi-Module Projects?
 
 Yes. You can use standard Maven modules in your application, or even external dependencies, as there is no need for endpoints and entity classes to be in the same project as the Hilla application. See <<../reference/configuration#java-compiler-options,Configuration>> for details.
 
 
-== Can I use Kotlin, Scala, or Groovy?
+== Does Kotlin, Scala, or Groovy Work with Hilla?
 
 Hilla is developed using Java as the reference language for the backend. Hilla parses `.class` files, which can be compiled from other languages as well, but support from some features may vary depending on the language. For example, in Java, an annotation is used to mark a field as not null, while in Kotlin that's part of the language syntax.
 
 
-== Does Hilla support a microservice architecture?
+== Does Hilla Support a Microservice Architecture?
 
-Yes. Hilla only requires a thin endpoint layer to communicate with the frontend. The rest of the backend can employ a microservice setup that Hilla endpoints would communicate with. See the https://hilla.dev/blog/using-microservices-from-hilla/[“Using microservices from Hilla”] blog post for more details.
+Yes. Hilla only requires a thin endpoint layer to communicate with the frontend. The rest of the backend can employ a microservice setup with which Hilla endpoints would communicate. See the https://hilla.dev/blog/using-microservices-from-hilla/["Using microservices from Hilla"] article for more details.
 
 // end::content[]