Skip to content

Commit 1363510

Browse files
authored
[EN]-AI training troubleshooting
1 parent b310513 commit 1363510

File tree

1 file changed

+4
-4
lines changed
  • pages/public_cloud/ai_machine_learning/training_guide_07_troubleshooting

1 file changed

+4
-4
lines changed

pages/public_cloud/ai_machine_learning/training_guide_07_troubleshooting/guide.en-gb.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -23,19 +23,19 @@ All steps for starting and working on AI Training are described in the [AI Train
2323

2424
When you use AI Training, make sure to mount Object Storage containers to your job. You will need to back up your files on these volumes. Once your training job is complete (status is `DONE` ), your job should synchronise your data on the mounted Object Storage container(s).
2525

26-
If no volumes are mounted in the specified location, your files will be saved in the job's local and ephemeral storage, then deleted once the job is finished.
26+
If no volumes are mounted in the specified location, your files will be saved in the job's local and ephemeral storage and then deleted once the job is finished.
2727

2828
### Which commands and arguments can I use to debug?
2929

3030
A lot of options and sub-commands are available in the ovhai CLI tool. This is the recommended means of interaction with AI Solutions. To install it, follow the [CLI Installation guide](/pages/public_cloud/ai_machine_learning/cli_10_howto_install_cli).
3131

32-
To get a list of available sub-commands and arguments, just start run:
32+
To get a list of available sub-commands and arguments, use the command:
3333

3434
``` {.bash}
3535
ovhai --help
3636
```
3737

38-
Further details on each sub-command can be accessed by:
38+
Further details on each sub-command can be accessed with:
3939

4040
``` {.bash}
4141
ovhai <subcommand> --help
@@ -116,7 +116,7 @@ You may now start your commands and/or use the typical commandline utils to debu
116116

117117
#### Debug your Code
118118

119-
The easiest way to debug your code may be using above interactive debug-session and run/compile your code interactively checking for:
119+
The easiest way to debug your code may be using the above interactive debug-session and run/compile your code interactively checking for:
120120

121121
- error-messages
122122
- syntax errors

0 commit comments

Comments
 (0)