Small edits (#796)

docs/integrations/autokeras.md

@@ -24,7 +24,7 @@ And that's it! This creates a [ClearML Task](../fundamentals/task.md) which capt
 * Scalars (loss, learning rates)
 * Console output
 * General details such as machine details, runtime, creation date etc.
-* Hyperparameters created with standard python packages (e.g. argparse, click, Python Fire, etc.)
+* Hyperparameters created with standard python packages (such as argparse, click, Python Fire, etc.)
 * And more
 
 You can view all the task details in the [WebApp](../webapp/webapp_exp_track_visual.md). 

docs/integrations/hydra.md

@@ -28,7 +28,7 @@ ClearML logs the OmegaConf as a blob and can be viewed in the
 ## Modifying Hydra Values
 
 ### Via Command Line
-You can use Hydra's command line syntax to modify your OmegaConf: override, append, or remove config values:
+You can use Hydra's command line syntax to modify your OmegaConf: override, append, or remove configuration values:
 * Override config value: `foo.bar=value`
 * Append config value: `+foo.bar=value`
 * Remove config value: `~foo.bar` or `~foo.bar=value`

docs/integrations/transformers.md

@@ -46,7 +46,7 @@ ClearML uses `/` as a delimiter for subprojects: using `example/sample` as a nam
 task within the `example` project. 
 :::
 
-In order to log the models created during training, set the `CLEARML_LOG_MODEL` environment variable to `True`. 
+To log the models created during training, set the `CLEARML_LOG_MODEL` environment variable to `True`. 
 
 You can see all the captured data in the task's page of the ClearML [WebApp](../webapp/webapp_exp_track_visual.md).