Merge pull request #1772 from alexpovel/main

Use unconstrained formatting pairs for possessive monospace

Author: ben

book/08-customizing-git/sections/attributes.asc

@@ -298,7 +298,7 @@ Now, when you run `git archive` to create a tarball of your project, that direct
 
 ===== `export-subst`
 
-When exporting files for deployment you can apply `git log`'s formatting and keyword-expansion processing to selected portions of files marked with the `export-subst` attribute.
+When exporting files for deployment you can apply ``git log```'s formatting and keyword-expansion processing to selected portions of files marked with the ``export-subst`` attribute.
 
 For instance, if you want to include a file named `LAST_COMMIT` in your project, and have metadata about the last commit automatically injected into it when `git archive` runs, you can for example set up your `.gitattributes` and `LAST_COMMIT` files like this:
 

book/B-embedding-git/sections/libgit2.asc

@@ -172,7 +172,7 @@ int git_odb_backend_mine(git_odb_backend **backend_out, /*…*/)
 }
 ----
 
-The subtlest constraint here is that `my_backend_struct`'s first member must be a `git_odb_backend` structure; this ensures that the memory layout is what the Libgit2 code expects it to be.
+The subtlest constraint here is that ``my_backend_struct```'s first member must be a ``git_odb_backend`` structure; this ensures that the memory layout is what the Libgit2 code expects it to be.
 The rest of it is arbitrary; this structure can be as large or small as you need it to be.
 
 The initialization function allocates some memory for the structure, sets up the custom context, and then fills in the members of the `parent` structure that it supports.