diff --git a/archetype-java-builders/src/main/resources/archetype-resources/src/main/resources/profiles/basic/environment.properties b/archetype-java-builders/src/main/resources/archetype-resources/src/main/resources/profiles/basic/environment.properties
index 409f9f547..3754c2ac6 100644
--- a/archetype-java-builders/src/main/resources/archetype-resources/src/main/resources/profiles/basic/environment.properties
+++ b/archetype-java-builders/src/main/resources/archetype-resources/src/main/resources/profiles/basic/environment.properties
@@ -49,7 +49,7 @@ jagger.load.scenario.id.to.execute=exampleJaggerLoadScenario
 #     proper Hibernate functionality
 #
 # NOTE:
-# - Default MySQL settings below corrspond to the MySQL docker container that is the part of Jagger distribution
+# - Default MySQL settings below correspond to the MySQL docker container that is the part of Jagger distribution
 # - If you would like to run your project without configuring DB, use H2 data base setting below
 
 chassis.storage.rdb.client.driver=com.mysql.jdbc.Driver
@@ -141,7 +141,7 @@ chassis.monitoring.command.execution.ttl=30000
 # Following settings are available for monitoring metrics
 # plotData - set true if you want to save metric vs time for plots
 # showSummary - set true if you want to save value for summary table
-# normalizationBy - possibility to normaliza metric vs time (possible values: NONE, SECOND, MINUTE, HOUR)
+# normalizationBy - possibility to normalize metric vs time (possible values: NONE, SECOND, MINUTE, HOUR)
 #
 # if both plotData and saveSummary are false, monitoring metric will be not saved
 #
@@ -186,7 +186,7 @@ chassis.engine.e1.reporting.session.comparison.baseline.session.id=#IDENTITY
 # # # Decision when no matching metric for limit is found # # #
 # Valid when you are using decision making with limits
 # Describes: What decision should be taken when limit is specified, but no metric in the test matches metricName of this Limit
-# Default: OK - because this is not critical (you can specify limits in advance - it doen't influence quality of results)
+# Default: OK - because this is not critical (you can specify limits in advance - it doesn't influence quality of results)
 # Allowed values (Decision enum): OK, WARNING, ERROR, FATAL
 chassis.decision.maker.with.limits.decisionWhenNoMetricForLimit=OK
 
@@ -212,14 +212,14 @@ chassis.decision.maker.with.limits.decisionWhenSeveralLimitsMatchSingleMetric=FA
 # ****************************************************************** #
 
 # # # Path to file with default properties # # #
-# Properties hierarhy:
+# Properties hierarchy:
 # Default properties -> Environment properties -> User properties -> System properties [higher priority]
 jagger.default.environment.properties=./configuration/basic/default.environment.properties
 
 # # # Comma separated list of paths to files with user properties # # #
 # You can use multiple property files f.e. for different environment configurations
 # or for different tests
-# Properties hierarhy:
+# Properties hierarchy:
 # Default properties -> Environment properties -> User properties -> System properties [higher priority]
 #jagger.user.environment.properties=./profile/basic/test_config1.properties,./profile/basic/sut_config.properties
 
@@ -300,7 +300,7 @@ report.session.comment=
 # Properties will influence aggregation interval of measured parameters
 # You can define exact interval between points,
 #   or you can define count of points and interval will be calculated
-# It is also possible to set interval or point count for every measured parameter separatly
+# It is also possible to set interval or point count for every measured parameter separately
 # See Aggregators documentation for more info
 
 chassis.engine.e1.reporting.task.type=count
@@ -356,7 +356,7 @@ report.enable.decisions.per.metric.highlighting=true
 
 # # # Jagger roles # # #
 # Use default value. In most cases it will fit requirements
-# As short emplanation of roles: if you will launch Jagger with REPORTER role,
+# As short explanation of roles: if you will launch Jagger with REPORTER role,
 # it will just compile report without generating any load
 # More info about roles you can get in docu
 # Comma-separated list of roles. When Jagger starts the corresponding services are launched
@@ -387,7 +387,7 @@ chassis.log.storage.bean=localFileStorage
 
 # # # Zookeeper # # #
 # Address and port of ZooKeeper Server
-# Should be detemined on each Node in distributed mode . 2181 default port
+# Should be determined on each Node in distributed mode . 2181 default port
 #chassis.coordinator.zookeeper.endpoint=172.56.45.222:2181
 
 # ZooKeeper session timeout
@@ -414,7 +414,7 @@ chassis.coordinator.zookeeper.root.node=/root-001
 # Http Server starts with that port on HTTP_COORDINATION_SERVER, 8089 - default
 #chassis.coordination.http.port=8089
 
-# Reconnect period of MASTER/KERNEL to COORDINATIONA_SERVER
+# Reconnect period of MASTER/KERNEL to COORDINATION_SERVER
 #chassis.coordinator.reconnect.period=5000
 
 # Minimum number of kernels expected by master
@@ -436,7 +436,7 @@ chassis.conditions.min.kernels.count=1
 #workload.threads.maxcount=4000
 
 # # # Serialization # # #
-# If true, jBoss serealisation will be used for communication between all nodes
+# If true, jBoss serialization will be used for communication between all nodes
 
 chassis.util.usejboss=true