DeviceLayout v1.4.2

CHANGELOG.md

@@ -4,12 +4,13 @@ The format of this changelog is based on
 [Keep a Changelog](https://keepachangelog.com/), and this project adheres to
 [Semantic Versioning](https://semver.org/).
 
-## Upcoming
+## 1.4.2 (2025-07-16)
 
   - Removed invalid keyword constructor without type parameters for `@compdef`-ed components with type parameters, so it can be overridden without warnings
   - Fixed `1` character in PolyTextSansMono
   - Fixed autofill exclusion in DemoQPU17
   - Removed stale Memoize.jl dependency
+  - Minor documentation improvements
 
 ## 1.4.1 (2025-07-08)
 

Project.toml

@@ -1,6 +1,6 @@
 name = "DeviceLayout"
 uuid = "ebf59a4a-04ec-49d7-8cd4-c9382ceb8e85"
-version = "1.4.1"
+version = "1.4.2"
 
 [deps]
 Accessors = "7d9f7c33-5ae7-4f3b-8dc6-eff91059b697"

docs/src/geometrylevel.md

@@ -98,11 +98,9 @@ nothing; # hide
 
 !!! info
 
-    The SVG backend only draws the top-level `Cell`, so it's necessary to [`flatten`](./geometry.md#Flattening) the cell before saving. `flatten` traverses references to place all entities in a single `Cell`, applying transformations as necessary.
+    The SVG backend only draws the top-level `Cell`, so it's necessary to [`flatten`](./geometry.md#Flattening) the cell before saving. `flatten` traverses references to place all entities in a single `Cell`, applying transformations as necessary. For further examples, we'll hide the line that flattens and saves to SVG just to display a cell.
 
-(For further examples, we'll hide the line that flattens and saves to SVG just to display a cell.)
-
-Of course, we can also add `Cell` references directly to a `Cell`, for example to apply a global rotation:
+We can also add `Cell` references directly to a `Cell`, for example to apply a global rotation:
 
 ```@example 1
 c_wrapper = Cell("wrapper", nm)
@@ -155,7 +153,7 @@ addref!(cs, p) # either render! or place! would do the same thing here
 refs(cs)
 ```
 
-Of course, eventually we'll want to turn this into a `Cell`. Since we were using named `SemanticMeta` layers, we just need to specify how to convert them to `GDSMeta`:
+Eventually, we'll still want to turn this into a `Cell`. Since we were using named `SemanticMeta` layers, we just need to specify how to convert them to `GDSMeta`:
 
 ```@example 1
 layer_record = Dict(:bridge => GDSMeta(1), :metal_negative => GDSMeta())

docs/src/units.md

@@ -70,9 +70,9 @@ If you want different behavior, then the recommended practice is to specify a un
 units = "PreferMicrons"
 ```
 
-then DeviceLayout will be compiled with `using .PreferMicrons` internally. (This is accomplished using [Preferences.jl](https://juliapackaging.github.io/Preferences.jl/stable/).) That means that `DeviceLayout.nm` and so on will prefer to be converted to microns, and `const UPREFERRED = DeviceLayout.μm`.
+then DeviceLayout will be compiled with `using .PreferMicrons` internally. (This is accomplished using [Preferences.jl](https://juliapackaging.github.io/Preferences.jl/stable/).) That means that `DeviceLayout.nm` and so on will prefer to be converted to microns, and `const UPREFERRED = DeviceLayout.μm; const PreferredUnits = PreferMicrons`.
 
-Similarly, if we have the preference `units = "NoUnits"`, then DeviceLayout uses `import Unitful: nm, ...` and `const UPREFERRED = Unitful.NoUnits; const PreferredUnits = PreferMicrons` internally.
+Similarly, if we have the preference `units = "NoUnits"`, then DeviceLayout uses `import Unitful: nm, ...` and `const UPREFERRED = Unitful.NoUnits; const PreferredUnits = PreferNoUnits` internally.
 
 ```@docs
     DeviceLayout.UPREFERRED