Address the suggestions

cli/ballerina-cli/src/main/resources/cli-help/ballerina-pull.help

@@ -1,5 +1,6 @@
 NAME
-       ballerina-pull - Fetch packages from Ballerina Central
+       ballerina-pull - Fetch packages from Ballerina Central or a custom
+       package repository
 
 SYNOPSIS
        bal pull <org-name>/<package-name>[:<version>]
@@ -15,10 +16,13 @@ DESCRIPTION
        Organizations are unique within a repository and can be mapped to an
        individual user or organization registered with the repository.
 
+       To download a package from a custom repository, configure it in the Settings.toml
+       file and pass the given id with the --repository flag.
+
 OPTIONS
        --repository
            Pull a package from a custom repository.
-           Repositories specified in the Settings.toml are only allowed.
+           The repository must be configured in the <USER_HOME>/.ballerina/Settings.toml file.
 
 
 EXAMPLES
@@ -31,5 +35,5 @@ EXAMPLES
            $ bal pull wso2/gmail:1.1.0
 
        Pull the '1.1.0' version of the 'gmail' connector in the 'wso2'
-       organization from wso2 custom repository.
+       organization from the github package repository defined in the Settings.toml file.
            $ bal pull wso2/gmail:1.1.0 --repository=wso2

cli/ballerina-cli/src/main/resources/cli-help/ballerina-push.help

@@ -1,19 +1,22 @@
 NAME
        ballerina-push - Push the Ballerina Archive (BALA) of the current package
-       to Ballerina Central or to the local repository
+       to a package repository
 
 SYNOPSIS
        bal push [OPTIONS] <bala-path>
 
 
 DESCRIPTION
        Push the Ballerina archive (.bala) of the current package to Ballerina
-       Central or to a local repository. Once the package is pushed to Ballerina
+       Central, local or a custom remote repository. Once the package is pushed to Ballerina
        Central, it becomes public and sharable and will be permanent.
 
        To be able to publish a package to Ballerina Central, you should sign in
        to Ballerina Central and obtain an access token.
 
+       To be able to publish a package to a custom remote repository, it must be defined
+       in the <USER_HOME>/.ballerina/Settings.toml file.
+
 
 OPTIONS
        --repository

compiler/ballerina-lang/src/main/java/io/ballerina/projects/internal/ProjectDiagnosticErrorCode.java

@@ -36,10 +36,10 @@ public enum ProjectDiagnosticErrorCode implements DiagnosticCode {
     MISSING_PKG_INFO_IN_BALLERINA_TOML("BCE5006", "missing.package.info"),
     DEPRECATED_PACKAGE("BCE5007", "deprecated.package"),
     BUILT_WITH_OLDER_SL_UPDATE_DISTRIBUTION("BCE5008", "built.with.older.sl.update.distribution"),
+    CUSTOM_REPOSITORY_NOT_FOUND("BCE5009", "custom.repository.not.found"),
     MODULE_NOT_FOUND("BCE5100", "module.not.found"),
     UNSUPPORTED_COMPILER_PLUGIN_TYPE("BCE5200", "unsupported.compiler.plugin.type"),
     CONFLICTING_PLATFORM_JAR_FILES("BCE5300", "conflicting.platform.jars.type"),
-    CUSTOM_REPOSITORY_NOT_FOUND("BCE5009", "custom.repository.not.found"),
     ;
 
     private final String diagnosticId;