Fix a couple of typos

Author: greenrobot

README.md

@@ -8,10 +8,10 @@ The **text content** is written in the markdown format and the [docs](docs/) fol
 
 Other resources:
 
-* **Images** are places in the [static/img/assets/](static/img/assets/) folder.
+* **Images** are placed in the [static/img/assets/](static/img/assets/) folder.
 * The **main navigation** is located in the [sidebars.ts](sidebars.ts) file.
 * The main **configuration** is done in the [docusaurus.config.ts](docusaurus.config.ts) file.
-* CSS styles are written in the [src/css/custom.css](src/css/custom.css) file.
+* Custom **CSS styles** to overwrite the theme's default are located in the [src/css/custom.css](src/css/custom.css) file.
 
 Notes regarding image file names: only use lowercase and no spaces.
 

docs/README.mdx

@@ -36,7 +36,7 @@ This is the ObjectBox documentation for our C and C++ APIs. We strive to provide
 Jobs: We're looking for a [C++ Developer](https://objectbox.io/jobs/objectbox-senior-c-plusplus-developer/) with a ❤️ for performant code
 :::
 
-Are you ready use ObjectBox? These two pages will get you up to speed:
+Are you ready to use ObjectBox? These two pages will get you up to speed:
 
 <div className="custom-nav-card">
   <a href="/installation" className="custom-nav-card-link">

docs/generator.mdx

@@ -36,7 +36,7 @@ This is the reference guide on the ObjectBox Generator, a build-time tool for Ob
 For an intro to the generator, see also the [installation guide](installation#objectbox-generator) and [Generating Binding Code](getting-started#generating-binding-code).
 :::
 
-When using ObjectBox within your project, you typically need two things: the runtime library and the the build-time ObjectBox Generator. The generator takes a data model (see [Entity Annotations](entity-annotations)) as input and generates `struct`s, a data model representation as code and additional glue code for a tight and fast integration of your individual data types and the ObjectBox API.
+When using ObjectBox within your project, you typically need two things: the runtime library and the build-time ObjectBox Generator. The generator takes a data model (see [Entity Annotations](entity-annotations)) as input and generates `struct`s, a data model representation as code and additional glue code for a tight and fast integration of your individual data types and the ObjectBox API.
 
 If you are using CMake, it's highly recommended to use the CMake integration of the ObjectBox Generator. For all other setups, triggering the generator in [standalone mode](generator#using-the-standalone-generator) is also supported.
 
@@ -57,7 +57,7 @@ Once you have the ObjectBox runtime library set up via `FetchContent` (see [inst
 find_package(ObjectBoxGenerator 4.0.0 REQUIRED)
 ```
 
-With that, the CMake funciton add\_obx\_schema is now available (see next section).
+With that, the CMake function add\_obx\_schema is now available (see next section).
 
 ### Add the schema with `add_obx_schema`
 

docs/installation.mdx

@@ -91,7 +91,7 @@ endif()
 
 add_executable(myapp main.cpp)
 target_link_libraries(myapp objectbox)
-```cmake
+```
 If you want to integrate the ObjectBox-Generator via CMake (as an alternative to offline installation and pre-generation of C++ sources), use the following snippet:
 
 ```cmake
@@ -105,9 +105,8 @@ add_obx_schema(
   INSOURCE # Opt-in: Generate in source directory
   CXX_STANDARD 11 # Defaults to C++14 otherwise
 )
-```cmake
-\
-If you want to use an ObjectBox Sync variant of the library, change the list line to: 
+```
+If you want to use an ObjectBox Sync variant of the library, change the `target_link_libraries` to: 
 
 ```cmake title="CMakeLists.txt"
 target_link_libraries(myapp objectbox-sync)

docs/store.mdx

@@ -97,7 +97,7 @@ obx_store_open(opt);
 Available since v0.21.0
 :::
 
-You can use ObjectBox alsofor non-persistent in-memory databases. To create a memory-backed store, use the directory prefix "`memory:`" and pick a name for the database to address it, e.g. “memory:myApp”. Apart from the special prefix, it's using the same "directory" option call:
+You can use ObjectBox also for non-persistent in-memory databases. To create a memory-backed store, use the directory prefix "`memory:`" and pick a name for the database to address it, e.g. “memory:myApp”. Apart from the special prefix, it's using the same "directory" option call:
 
 <Tabs>
 <TabItem value="cpp" label="C++">
@@ -355,5 +355,3 @@ Once you created the store, it gives you access to several ways to interact with
 * [**Box API**](getting-started#working-with-object-boxes)**:** easy to use object-based API with implicit transactions. It is used in combination with the ObjectBox Generator, which generates the source code for data and Box classes. Check the getting started track for examples.
 * [**Query API**](queries)**:** In combination with the Box API, you can build powerful queries using the query builder. Once built, query instances can be executed multiple times to retrieve data.&#x20;
 * [**Explicit Transactions**](transactions)**:** Often it's a good idea to group several operations into a single "batch", or more precisely, one transaction. Batched transactions are not only faster, but also consider safe state changes for your data.
-
-