Final cleanups for documentation markdown files

.gitignore

@@ -9,6 +9,7 @@ package-lock.json
 /build
 /dist
 /data
+/temp
 /output
 /specs/data/output
 /specs/data/migration/output_gltf

CHANGES.md

@@ -1,7 +1,7 @@
 Change Log
 ==========
 
-### 0.4.1 - 2024-mm-dd
+### 0.4.1 - 2024-02-20
 
 - The packages that have been introduced in version `0.4.0` have been merged back into a single package.
   Details about the structure can be found in the [implementation notes](./IMPLEMENTATION.md).

IMPLEMENTATION.md

@@ -42,7 +42,7 @@ Generating the documentation consists of two steps (which are subcommands of the
 - extracting the API definitions from the build output
 - generating the markdown from the API definitions.
 
-The first step is performed by running `api-extractor` for each package individually. This happens from the top-level package JSON file, using the `--workspaces` parameter. The surface API information will be written into `./etc/<package>.md`. These files capture the public API, and changes in the public API will cause a warning to be printed
+The first step is performed by running `api-extractor`. The surface API information will be written into `./etc/3d-tiles-tools.md`. This file captures the public API, and changes in the public API will cause a warning to be printed
 
 > Warning: You have changed the public API signature for this project.
 

README.md

@@ -359,7 +359,7 @@ When the tools are not installed as a package from NPM, but supposed to be used
 
 After this, the tools can be executed using the same command line options as described above - for example:
 ```
-npx ts-node .\packages\cli\src\main.ts gzip -i ./specs/data/TilesetOfTilesets/ -o ./output/TilesetOfTilesets-gzipped/
+npx ts-node .\src\cli\main.ts gzip -i ./specs/data/TilesetOfTilesets/ -o ./output/TilesetOfTilesets-gzipped/
 ```
 
 See the [implementation notes](IMPLEMENTATION.md) for details about the project structure.