Apply suggestions from code review

Co-authored-by: Markus Hauru <[email protected]>

Author: penelopeysm

HISTORY.md

@@ -19,7 +19,7 @@ end
 end
 ```
 
-and the `inner.x` variable will be correctly conditioned.
+and the `a.x` variable will be correctly conditioned.
 (Previously, you would have to condition `inner()` with the variable `a.x`, meaning that you would need to know what prefix to use before you had actually prefixed it.)
 
 ### AD testing utilities

docs/src/api.md

@@ -78,9 +78,9 @@ decondition
 
 ## Fixing and unfixing
 
-We can also _fix_ a collection of variables in a [`Model`](@ref) to certain using [`DynamicPPL.fix`](@ref).
+We can also _fix_ a collection of variables in a [`Model`](@ref) to certain values using [`DynamicPPL.fix`](@ref).
 
-This might seem quite similar to the aforementioned [`condition`](@ref) and its siblings,
+This is quite similar to the aforementioned [`condition`](@ref) and its siblings,
 but they are indeed different operations:
 
   - `condition`ed variables are considered to be _observations_, and are thus

test/contexts.jl

@@ -105,7 +105,6 @@ Base.IteratorEltype(::Type{<:AbstractContext}) = Base.EltypeUnknown()
                     vcat,
                     pairs(conditioned_values),
                 )
-                @show conditioned_vns
 
                 # We can now loop over them to check which ones are missing. We use
                 # `getvalue` to handle the awkward case where sometimes