docs: fix spelling errors

src/app/components/Header/SaveLoadFileButton.tsx

@@ -93,8 +93,8 @@ const SaveLoadFileButton = ({
           </div>
         }
         items={[
-          ["Save file", exportToJSON],
-          ["Load JSON file", onOpen],
+          [t("save"), exportToJSON],
+          [t("load"), onOpen],
         ]}
       />
 

src/pages/docs/index.mdx

@@ -13,7 +13,7 @@ aggregations, subclass/superclass, n-ary relationships, cardinality and particip
 
 ## Examples
 
-An ER document is composed by a sequence of entity, relationship or aggregation declarations. The following example features ternary relationships, weak entities, inheritance and other concepts of the ER model:
+An ER document is composed of a sequence of entity, relationship or aggregation declarations. The following example features ternary relationships, weak entities, inheritance and other concepts of the ER model:
 ```erdoc
 entity Employee {
     e_id key

src/pages/docs/syntax/_meta.json

@@ -1,6 +1,6 @@
 {
   "entity": "Entity",
-  "weak_entity": "Weak entity",
   "relationship": "Relationship",
+  "weak_entity": "Weak entity",
   "aggregation": "Aggregation"
 }

src/pages/docs/syntax/aggregation.mdx

@@ -6,7 +6,7 @@ import { Callout } from "nextra/components";
 # Aggregation expression
 
 The syntax to define an aggregation -a virtual entity- uses the `aggregation` keyword, followed by the name of the aggregation and the name of the 
-relationship to be aggregated surrounded by parenthesis. The following example defines an aggregation named "Human_drinks_coffe" that aggregates the
+relationship to be aggregated surrounded by parenthesis. The following example defines an aggregation named "Human_drinks_coffee" that aggregates the
 "Drinks" relationship:
 
 ```erdoc

src/pages/docs/syntax/entity.mdx

@@ -17,7 +17,7 @@ The following example declares an entity with the name "Dog" which has the attri
   ```
   ## Entity attributes
   An entity attribute may be declared as a key attribute by adding the keyword `key` after the attribute name. Also, the ERdoc language allows attributes
-  to be composite following the `attribute: [part1, part2, partN]` syntax. The following example shows and entity with a composite attribute that is also 
+  to be composite following the `attribute: [part1, part2, partN]` syntax. The following example shows an entity with a composite attribute that is also 
   part of the key of the entity. 
   ```erdoc
   entity Company_Branch {

src/pages/docs/syntax/weak_entity.mdx

@@ -8,7 +8,7 @@ import { Callout } from 'nextra/components'
 The syntax for weak entities is very similar to the one for entities. To declare an entity as weak, we use the `depends on` keyword followed by the name of
 its identifying relationship.
 Since weak entities don't have keys but _partial keys_, we use the `pkey` keyword to declare an attribute as part of the partial key of a weak entity.
-Weak entities can have [composite attributes](/docs/Syntax/entity#entity-attributes) just as regular entities. Weak entities **can't** extend
+Weak entities can have [composite attributes](/docs/Syntax/entity#entity-attributes) just like regular entities. Weak entities **can't** extend
 other entities.
 
  In the following example, the weak entity "Assignment" depends on the entity "Course" through the relationship