Consistantify --profile useage

Author: theotherjimmy

docs/tools/CLI/cli-compile.md

@@ -42,7 +42,7 @@ The arguments for *compile* are:
 - `--source <SOURCE>` selects the source directory. The default is `.` (the current directory). You can specify multiple source locations, even outside the program tree.
 - `--build <BUILD>` selects the build directory. Default: `BUILD/` inside your program root.
    <span class="notes">**Note**: `mbed compile` ignores the current build directory; creating multiple build directories leads to errors.</span>
-- `--profile <PATH_TO_BUILD_PROFILE>` selects a path to a build profile configuration file. Example: `mbed-os/tools/profiles/debug.json`. See the dedicated [build profile documentation](/docs/tools/CLI/build_profiles.html) for more detail.
+- `--profile <PATH_TO_BUILD_PROFILE>` selects a path to a build profile configuration file. Example: `debug`. See the dedicated [build profile documentation](/docs/tools/CLI/build_profiles.html) for more detail.
 - `--library` compiles the code as a [static `.a/.ar` library](#compiling-static-libraries).
 - `--no-archive` suppresses the creation of `.a/.ar` files created by `--library`, producing many `.o` files instead.
    <span class="notes">**Note**: This option does nothing without `--library`.</span>
@@ -128,10 +128,10 @@ $ mbed compile -t GCC_ARM -m K64F -c -DUVISOR_PRESENT
 
 ##### Compile in debug mode
 
-To compile in debug mode (as opposed to the default *develop* mode), use `--profile mbed-os/tools/profiles/debug.json` in the compile command-line:
+To compile in debug mode (as opposed to the default *develop* mode), use `--profile debug` in the compile command-line:
 
 ```
-$ mbed compile -t GCC_ARM -m K64F --profile mbed-os/tools/profiles/debug.json
+$ mbed compile -t GCC_ARM -m K64F --profile debug
 ```
 
 

docs/tools/CLI/debug_builds_cli.md

@@ -21,19 +21,19 @@ $ mbed compile -o debug-info
 **Arm Mbed 2.0**
 
 ```
-$ mbed compile --profile .temp/tools/profiles/debug.json
+$ mbed compile --profile debug
 ```
 
 ### Exporting with debug symbols
 
 You can also enable debug symbols when [exporting your project](exporting.html) by using:
 
 ```
-$ mbed export -i uvision -m K64F --profile mbed-os/tools/profiles/debug.json
+$ mbed export -i uvision -m K64F --profile debug
 ```
 
 Make release builds by using:
 
 ```
-$ mbed export -i uvision -m K64F --profile mbed-os/tools/profiles/default.json
+$ mbed export -i uvision -m K64F --profile release
 ```

docs/tools/debug/debug_intro.md

@@ -24,7 +24,7 @@ In your project folder, run:
 # alternatively, use -i make_armc5 for ARMCC, or -i make_iar for IAR
 # replace K64F with your target board
 
-$ mbed export -i make_gcc_arm -m K64F --profile mbed-os/tools/profiles/debug.json
+$ mbed export -i make_gcc_arm -m K64F
 ```
 
 ##### Serial terminal

docs/tutorials/debug/eclipse_pyocd.md

@@ -43,7 +43,7 @@ In your project folder, run:
 # Replace K64F with your target board
 # If you're not using GCC ARM, use -i eclipse_armc5 for ARMCC, or -i eclipse_iar for IAR
 
-$ mbed export -i eclipse_gcc_arm -m K64F --profile mbed-os/tools/profiles/debug.json
+$ mbed export -i eclipse_gcc_arm -m K64F --profile debug
 ```
 
 ### Importing the project in Eclipse
@@ -121,5 +121,5 @@ We build using Make, but you can also use Mbed CLI for building from Eclipse:
 1. Go to *Project > Properties > C/C++ Build*.
 1. Remove the check *Use default build command*.
 1. Set *Build command* to `mbed`.
-1. Under *Behavior* > *Build (Incremental build)*, select your Mbed CLI build options. For example: `compile -m K64F -t GCC_ARM --profile ${CWD}mbed-os/tools/profiles/debug.json`.
+1. Under *Behavior* > *Build (Incremental build)*, select your Mbed CLI build options. For example: `compile -m K64F -t GCC_ARM --profile debug`.
 1. Make sure to update the paths to the `.elf` file in your debug configuration.

docs/tutorials/debug/keil_uvision.md

@@ -23,7 +23,7 @@ To export your project to uVision, you can use either the Online Compiler or Mbe
 
     ```
     # replace K64F with your target board
-    $ mbed export -i uvision5 -m K64F --profile mbed-os/tools/profiles/debug.json
+    $ mbed export -i uvision5 -m K64F
     ```
 
 ### Starting a debug session

docs/tutorials/debug/vs_code.md

@@ -40,7 +40,7 @@ In your project folder, run:
 # alternatively, use -i vscode_armc5 for ARMCC, or -i vscode_iar for IAR
 # replace K64F with your target board
 
-$ mbed export -i vscode_gcc_arm -m K64F --profile mbed-os/tools/profiles/debug.json
+$ mbed export -i vscode_gcc_arm -m K64F --profile debug
 ```
 
 ### Configuring the debugger