docs(@schematics/angular): correct directory and entryFile option descriptions

The `ng new` `directory` option claimed the workspace is created in the current
directory when the option is omitted, but a new directory named after the
workspace is created instead. The library `entryFile` option described a path
relative to the workspace root, but the value is a file name without the `.ts`
extension that is placed in the library's `src` directory.

Author: MeAkib

packages/schematics/angular/library/schema.json

@@ -19,7 +19,7 @@
     "entryFile": {
       "type": "string",
       "format": "path",
-      "description": "The path to the library's public API file, relative to the workspace root. This file defines what parts of the library are accessible to applications that import it.",
+      "description": "The name of the library's public API file, without the `.ts` extension, relative to the library's `src` directory. This file defines what parts of the library are accessible to applications that import it.",
       "default": "public-api"
     },
     "prefix": {

packages/schematics/angular/ng-new/schema.json

@@ -8,7 +8,7 @@
   "properties": {
     "directory": {
       "type": "string",
-      "description": "The directory where the new workspace and project should be created. If not specified, the workspace will be created in the current directory."
+      "description": "The directory where the new workspace and project should be created. If not specified, a new directory named after the workspace is created in the current directory."
     },
     "name": {
       "description": "The name for the new workspace and the initial project. This name will be used for the root directory and various identifiers throughout the project.",